Status Update
Comments
as...@chromium.org <as...@chromium.org> #2
[Empty comment from Monorail migration]
mm...@chromium.org <mm...@chromium.org> #3
Sorry I didn't get back to you sooner, overlooked the bug. Are you still having this problem? I can't reproduce it on the latest stable version (16.0.912.75).
da...@gmail.com <da...@gmail.com> #4
I can reproduce this error by filling out this form and clicking submit:
https://quiltvertiser.danemcoweb.com/accounts/register/publisher/
The browser sits for about 60 seconds and then comes back with:
No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
However, the page submit and comes right back without any trouble when using Firefox 9.0 and Internet Explorer.
This is my version of Google Chrome:
Google Chrome 16.0.912.75 (Official Build 116452)
OS Linux
WebKit 535.7 (@103989)
JavaScript V8 3.6.6.15
Flash 11.1 r102
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Command Line /opt/google/chrome/google-chrome --flag-switches-begin --enable-print-preview --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/dpurcell/.config/google-chrome/Default
I can reproduce the problem in the Windows version of Google Chrome 16.
The browser sits for about 60 seconds and then comes back with:
No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
However, the page submit and comes right back without any trouble when using Firefox 9.0 and Internet Explorer.
This is my version of Google Chrome:
Google Chrome 16.0.912.75 (Official Build 116452)
OS Linux
WebKit 535.7 (@103989)
JavaScript V8 3.6.6.15
Flash 11.1 r102
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.75 Safari/535.7
Command Line /opt/google/chrome/google-chrome --flag-switches-begin --enable-print-preview --flag-switches-end
Executable Path /opt/google/chrome/google-chrome
Profile Path /home/dpurcell/.config/google-chrome/Default
I can reproduce the problem in the Windows version of Google Chrome 16.
mm...@chromium.org <mm...@chromium.org> #5
danielpurcell: That problem is almost certainly caused by the server not supporting the request headers and post data being split across different responses in HTTPS requests. There'll be a workaround for that in M17.
The issue reported in this bug report isn't a POST, so it's presumably a different problem.
The issue reported in this bug report isn't a POST, so it's presumably a different problem.
da...@gmail.com <da...@gmail.com> #6
mmenke: Thanks for the quick reply. I see -- so the issue here is that my server (quiltvertiser.danemcoweb.com ) doesn't accept POST data split across responses in HTTPS requests? Why would it work without any trouble in Firefox but break in Chrome? Does Chrome send the requests differently?
mm...@chromium.org <mm...@chromium.org> #7
FireFox and IE have the workaround we just added. I believe the original problem was caused when we added support for chunk-encoded/streaming input for POST bodies, which resulted in separating out the code to send the header and the body, since we now might not always have the body when sending the headers.
I've tested the page on Chrome 18 (Don't have 17 handy), and it seems to work fine. I was also able to reproduce the issue in Chrome 16, so presumably not due to differences in our internet connection/network configurations.
I'm not sure about the exact timeline for Chrome 17's release, but think it'll be sometime in the next couple weeks.
I've tested the page on Chrome 18 (Don't have 17 handy), and it seems to work fine. I was also able to reproduce the issue in Chrome 16, so presumably not due to differences in our internet connection/network configurations.
I'm not sure about the exact timeline for Chrome 17's release, but think it'll be sometime in the next couple weeks.
da...@gmail.com <da...@gmail.com> #8
Thank you very much. Are you aware of anything I can do on the server-side to solve this problem at this time?
mm...@chromium.org <mm...@chromium.org> #9
You could try and fix the server's code to parse HTTPS requests. This could be a significant undertaking or a trivial fix, depending on the software it's running.
mm...@chromium.org <mm...@chromium.org> #10
Parse the split HTTPS requests, rather.
da...@gmail.com <da...@gmail.com> #11
OK, thanks. I'm using lighttpd and apache (both are experiencing the same behavior), so I'll need to dive into it to see what can be done. Thanks for your insight.
mm...@chromium.org <mm...@chromium.org> #12
danielpurcell: The issue used to track that bug is https://crbug.com/chromium/107966 , though not sure there's any more info there that will be of use to you.
Back to the issue at hand: ltreugene, now that I look at what happens when loading that site, it's actually also the POST issue danielpurcell is encountering, so I'm going to go ahead and merge this bug.
Back to the issue at hand: ltreugene, now that I look at what happens when loading that site, it's actually also the POST issue danielpurcell is encountering, so I'm going to go ahead and merge this bug.
bu...@chromium.org <bu...@chromium.org> #14
[Empty comment from Monorail migration]
ef...@chromium.org <ef...@chromium.org> #15
[Empty comment from Monorail migration]
[Monorail components: Internals>Network]
[Monorail components: Internals>Network]
ef...@chromium.org <ef...@chromium.org> #16
[Empty comment from Monorail migration]
[Monorail components: -Internals>Network>HTTP]
[Monorail components: -Internals>Network>HTTP]
is...@google.com <is...@google.com> #17
This issue was migrated from crbug.com/chromium/108714?no_tracker_redirect=1
[Multiple monorail components: Internals, Internals>Network]
[Monorail mergedinto:crbug.com/chromium/107966 ]
[Monorail components added to Component Tags custom field.]
[Multiple monorail components: Internals, Internals>Network]
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description
Chrome Version : <Copy from: 'about:version'>
OS Version: OS X 10.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
What is the expected result?
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
What happens instead?
Please provide any additional information below. Attach a screenshot if
possible.