search

weeping / ratproxy

Automatically exported from code.google.com/p/ratproxy
0 stars 0 forks source link

several ambiguous HTTP content headers message #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run ratproxy with low verbosity (-lfscm)
2. Browse a web application.
3. Watch Several log messages (correct?)

What is the expected output? What do you see instead?
Several "Ambiguous HTTP content headers" message browsing web application
with js scripts.
3|3|Ambiguous HTTP content
headers|-|304|0|-|-|-|-|GET|https://jira-application:443/s/233/1/1.0/_/download/
resources/jira.webresources:scriptaculous/controls.js|-|-|-

What version of the product are you using? On what operating system?
ratproxy version 1.51-beta 
ubuntu 8.04

Please provide any additional information below.

HTTP request/response example triggering "Ambiguous HTTP content headers"
message.

https://jira-applictaion/s/233/1/1.0/_/download/resources/jira.webresources:scri
ptaculous/controls.js

GET
/s/233/1/1.0/_/download/resources/jira.webresources:scriptaculous/controls.js
HTTP/1.1

Host: jira-application
User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9)
Gecko/2008061015 Firefox/3.0

Accept: */*

Accept-Language: es-es,es;q=0.8,en-us;q=0.5,en;q=0.3

Accept-Encoding: gzip,deflate

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

Keep-Alive: 300

Connection: keep-alive

Referer: https://jira-application/secure/Dashboard.jspa

Cookie: JSESSIONID=XXXXXXXXXXA456698C1FCF906457CE74

If-Modified-Since: Tue, 22 May 2007 07:00:00 GMT

If-None-Match: W/"28803-1179817200000"

HTTP/1.x 304 Proxied response

Connection: close

Content-Length: 0

Server: Apache-Coyote/1.1

Pragma: No-cache

Cache-Control: max-age=315360000000, private

Expires: Fri, 06 Jul 2018 12:32:30 GMT

Date: Tue, 08 Jul 2008 12:32:29 GMT

What's the exact problem with this HTTP requests/response?

Thanks

Original issue reported on code.google.com by ecasbas on 8 Jul 2008 at 12:45

GoogleCodeExporter commented 9 years ago 
I can't provide you with specific advice about your internal applications. 
There are
two reasons for this message, however:

1) Duplicate headers in HTTP response (please examine with curl -i <URL>, as the
headers displayed by ratproxy already have dupes eliminated).

2) Character set declared in HTTP headers and in HTML payload do not match.

If you believe that the message is reported in error (for example, there is a
duplicate header, but it is harmless or expected), please let me know.

Original comment by lcam...@gmail.com on 9 Jul 2008 at 8:43