The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
A requesting POST method does not allow a redirect due to the specification of RFC 2616. A hardware appliance solution handles the 302-idempotent redirect resulting from the Post Redirect Get (PRG) pattern.
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
93% of the total text.
Page 1 of 2
Method Of Handling An Idempotent 302 Redirect with RFC 2616 Compliant Hardware Appliance
The present invention comprises a method of handling an idempotent 302 redirect with a RFC 2616 compliant hardware appliance. The hardware appliance handles the redirect (see Fig.) using the following method:
1. Establish appliance logic to prevent default redirection 2. Identify occurrence of a 302 Post Redirect Get (PRG) 3. Execute a hardware process rule a. Modify HTTP header information b. Process redirect
Note: The redirection remedies the specification of RFC 2616, which disallows a requesting POST method to perform a redirect (Section 10.3). Most portal server applications interpret this specification loosely during the login process and allow the idempotent redirection to occur. The problem becomes apparent when a network appliance that adheres to the RFC 2616 emerges in front of such a portal server application. The appliance will not allow for the redirect of an idempotent 302 redirect to a POST method.
1. Disable the follow redirect option 2. Create rule Match action on 302 PRG 3. Execute processing rule to call xsl transformation activities 4. Use DP extensions to pull and reset: a. URL variable b. Header 'location' c. 302 moved code