Problem with content engine 5.5.19

[bala020881]

Dear All,

While accessing website using this proxy I'm facing some issues, but if I access without proxy it works fine.

WITH PROXY

Response Headerspretty print

HTTP/1.1 302 Object moved

Server: Microsoft-IIS/5.0

Date: Wed, 22 Dec 2010 08:33:16 GMT

X-Powered-By: ASP.NET

Location: welcome.asp

Content-Length: 132

Content-Type: text/html

Cache-Control: private

Proxy-Connection: Close

Request Headerspretty print

POST http://xxx.com/submit_form.asp HTTP/1.1

Host: xxx.com

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729)

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Accept-Language: en-us,en;q=0.5

Accept-Encoding: gzip,deflate

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7

Keep-Alive: 115

Proxy-Connection: keep-alive

Referer: http://xxx.com/welcome.asp

Cookie: ASPSESSIONIDSAQTRQQR=GFCJOKHBFAJCBNBKDEOEONNA; ASPSESSIONIDSCDQQDAA=IMIELKDBOOBDMIJGEEJMGFFO

WITHOUT PROXY

Response Headerspretty print

HTTP/1.1 302 Object moved

Server: Microsoft-IIS/5.0

Date: Wed, 22 Dec 2010 08:38:03 GMT

X-Powered-By: ASP.NET

Pragma: no-cache

Cache-Control: private, no-cache

Location: simple.asp

Content-Length: 131

Content-Type: text/html

Expires: Tue, 21 Dec 2010 08:38:02 GMT

Request Headerspretty print

GET /welcome.asp HTTP/1.1

Host:xxx.com

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729)

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Accept-Language: en-us,en;q=0.5

Accept-Encoding: gzip,deflate

Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7

Keep-Alive: 115

Connection: keep-alive

Referer: http://xxx.com/welcome.asp?language=E

Cookie: ASPSESSIONIDSAQTRQQR=GFCJOKHBFAJCBNBKDEOEONNA; ASPSESSIONIDSCDQQDAA=IMIELKDBOOBDMIJGEEJMGFFO

Can someone help me to fix this issue in content engine

Regards

Balajirajah P B

[sachinga.hcl]

Hi Bala,

As you can see that with proxy the POST method is there like

POST http://xxx.com/submit_form.asp HTTP/1.1

While without proxy the method used s GET as follows:

GET /welcome.asp HTTP/1.1

SO check on your content engine for which method is needed to present the correct page.

As their names imply, both HTTP GET and HTTP POST use HTTP as their underlying protocol. Both of these methods encode request parameters as name/value pairs in the HTTP request.

The GET method creates a query string and appends it to the script's URL on the server that handles the request.

The POST method creates a name/value pairs that are passed in the body of the HTTP request message.

We can send data to the data processing page by both the GET and POST methods of a form. Both methods are used in form data handling where each one has some difference on the way they work. We will discuss some of the differences.

As you have seen there is a character restriction of 255 in the URL. This is mostly the old browsers restriction and new ones can handle more than that. But we can't be sure that all our visitors are using new browsers. So when we show a text area or a text box asking users to enter some data, then there will be a problem if more data is entered. This restriction is not there in POST method.

In GET method data gets transferred to the processing page in name value pairs through URL, so it is exposed and can be easily traced by visiting history pages of the browser. So any login details with password should never be posted by using GET method.

As the data transfers through address bar ( URL ) there are some restrictions in using space, some characters like ampersand ( & ) etc in the GET method of posting data. We have to take special care for encoding ( while sending ) and decoding ( while receiving ) data if such special characters are present.

There are some special cases where advantage of using GET method is , one can store the name value pairs as bookmark and directly use them by bypassing the form.

Kindly check  the below mentione URL for more details on GET or POST method:

http://www.diffen.com/difference/Get_vs_Post

HTH

Sachin GARG