Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate headers received when using temporary bypass #29

Closed
thanegill opened this issue Aug 21, 2014 · 11 comments
Closed

Duplicate headers received when using temporary bypass #29

thanegill opened this issue Aug 21, 2014 · 11 comments

Comments

@thanegill
Copy link
Contributor

screen shot 2014-08-21 at 2 49 53 pm

The response from the server contained duplicate headers. This problem is generally the result of a misconfigured website or proxy. Only the website or proxy administrator can fix this issue. Error code: ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION

Using IP auth with a temporary bypass link. Works in safari on OS X, But nowhere else.

Built with:  '--prefix=/usr' '--sysconfdir=/etc' '--localstatedir=/var' '--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' '--enable-email=yes' '--with-proxyuser=e2guardian' '--with-proxygroup=e2guardian' '--with-filedescriptors=65536' 'CXXFLAGS=-DFD_SETSIZE=65536'

Custom block page: https://github.com/visd/e2guardian-install/blob/master/template.html

Wireshark capture: http://cl.ly/1o203j411z18 (Now with response)

@fredbcode
Copy link
Contributor

Please, can you make a try with a browser plug-in like LiveHTTPHeaders (firefox)

@thanegill
Copy link
Contributor Author

This is my go at LiveHTTPHeaders on chrome: The first is the initial request, and the second the just seems to be blank, meaning no requests.
screen shot 2014-08-22 at 9 28 33 am

I don't think that LiveHTTPHeaders was even receiving the headers. These are the response headers that I got out the the wireshark capture (there's an updated version above that includes the response that the initial one didn't have.)

screen shot 2014-08-22 at 9 56 06 am

@thanegill
Copy link
Contributor Author

One possibility is that the extra CRLF ("\r\n") after the location header in the 302 redirect is what is causing the problem. In RFC 2616 according to the last paragraph is section 4.1 it's states that HTTP/1.1 clients should not follow any requests that have an extra CRLF.

@fredbcode
Copy link
Contributor

Can you make a short test with http://numsys.eu/TMP/e2guardian.zip
There is always the extra CRLF ?

@thanegill
Copy link
Contributor Author

Just tried it. Having the same issues.

@fredbcode
Copy link
Contributor

\r\n ?

@fredbcode
Copy link
Contributor

Ok I found something, please make a try with http://numsys.eu/TMP/e2guardian.tar.gz

@fredbcode
Copy link
Contributor

Works with seven - firefox 30 and IE10 -

@thanegill
Copy link
Contributor Author

Tested and works in Firefox 31.0 for OS X, Safari 8.0 for OS X, Chrome 36 on Windows, IE11 on windows.

Does not work on Chrome for OS X. Might be a bug in Chrome...

@fredbcode
Copy link
Contributor

OK great, yes it should be
Can you check if it accept the cookie ?

fredbcode pushed a commit that referenced this issue Aug 28, 2014
fredbcode pushed a commit that referenced this issue Aug 28, 2014
fredbcode pushed a commit that referenced this issue Aug 28, 2014
@fredbcode
Copy link
Contributor

Fixed in 3.0.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants