Issue metadata
Sign in to add a comment
|
Browser says: "forums.opensuse.org sent an invalid response"
Reported by
stu...@anchev.net,
Mar 22 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Example URL: https://forums.opensuse.org/showthread.php/.....?goto=newpost Steps to reproduce the problem: 1. Subscribe to a thread in forums.opensuse.org 2. Wait a few hours 3. After someone replies and you receive the notification email click the link. It should look like this: https://forums.opensuse.org/showthread.php/.....?goto=newpost Result: Chromium says: The forums.opensuse.org page isn’t working forums.opensuse.org sent an invalid response. ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION 4. Remove the part "?goto=newpost" from the URL and visit the link created this way. It will take you to the home of the forum: forums.opensuse.org 5. Go back to the notification email and click the link (the one with the ?goto=newpost end) Result: Now the thread page opens as expected. What is the expected behavior? To see the forum thread page properly. What went wrong? Chromium says: The forums.opensuse.org page isn’t working forums.opensuse.org sent an invalid response. ERR_RESPONSE_HEADERS_MULTIPLE_LOCATION Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 49.0.2623.87 Channel: stable OS Version: openSUSE Leap 42.1 Flash Version: Shockwave Flash 20.0 r0 This was previously discussed in this forum thread: https://forums.opensuse.org/showthread.php/509317-Problem-with-the-forum-using-Chrome
,
Mar 22 2016
Thanks for the report. Could you provide a net-internals dump to help us triage this issue further? Instructions here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details .
,
Mar 22 2016
Hi, I am not sure if I can do this correctly and without sending any inappropriate data (e.g. private info). But you can easily reproduce the bug following the steps described above. Also you can collaborate with the experts from SUSE where I have reported the same bug: https://bugzilla.opensuse.org/show_bug.cgi?id=972188 According to the comment I read there it seems that might be a mix of browser and server miscommunication. So please if possible discuss this with the other experts. I am not really an expert.
,
Mar 23 2016
Thank you for providing more feedback. Assigning to requester "xunjieli@chromium.org" for another review. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2016
,
Mar 23 2016
Chrome doesn't allow multiple location headers in the same response. See https://crbug.com/146684
,
Mar 23 2016
This happens when a page tells us to go to two different locations. Other browsers may pick the first location, or the last. Chrome considers it a fatal error. This is working as intended, the site should be fixed to tell Chrome what it really wants Chrome to do. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by csharrison@chromium.org
, Mar 22 2016