incomplete chunked encoding error shows blank page (Chrome shows error)
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
People
(Reporter: dietrich, Unassigned)
Details
(Keywords: DevAdvocacy, Whiteboard: [DevRel:P2])
URL that caused this: http://www.oregonlive.com However, I'm sure it'll be fixed soon :P Screenshot of Chrome: https://i.imgur.com/hOhRAyH.png Firefox nightly and release on both desktop and mobile all show a blank white page.
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Updated•8 years ago
|
Updated•7 years ago
|
Comment 1•7 years ago
|
||
I have tested the reported issue on Windows 10 and OS X 10.12 on Firefox Release and latest Nightly builds (Chrome as well). I could not reproduce the issue on any platform. I will mark this as Resolved:WorksForMe. If anyone can still reproduce the issue, feel free to reopen it and provide more information.
Reporter | ||
Comment 2•7 years ago
|
||
Hi Stefan. Can you please say how you tested it? If you tested against the original URL, then please re-open it. To definitively close the issue, you'll need to recreate the scenario described and confirm that we no longer show a blank white page.
Comment 3•7 years ago
|
||
Hi Dietrich, I've tested the issue with the provided details. I've visited the page with new profile and verified that nothing is broken. Page is opened and rendered without issue. Please provide more detailed information or STR on how to reveal the issue.
Reporter | ||
Comment 4•7 years ago
|
||
Yep, the website likely fixed the issue. We need someone from necko team to take it from here. They'll know best how to construct the right conditions for re-creating the problem and make sure we're showing a neterror page. Patrick, can you have someone on your team take a look?
Updated•7 years ago
|
Comment 5•7 years ago
|
||
Not sure when we'll get to this. If I see better steps to reproduce and/or more bug reports of this behavior it'll float to the top of the queue faster.
Comment 6•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598
I believe this is because Firefox fails to require last-chunk in Transfer-Encoding: chunked. While other browsers mark transfers not containing such chunk as incomplete/failed, Firefox marks them as completed/success.
This is even mentioned in https://bugzilla.mozilla.org/show_bug.cgi?id=654577:
This bug is not about a failure to require a last-chunk.
Reproduction steps are as follows:
➜ cat chunked.txt
HTTP/1.2 200 OK
Connection: close
Content-Type: application/octet-stream; charset=binary
Transfer-Encoding: chunked
1
a
➜ od -a chunked.txt
0000000 H T T P / 1 . 2 sp 2 0 0 sp O K cr
0000020 nl C o n n e c t i o n : sp c l o
0000040 s e cr nl C o n t e n t - T y p e
0000060 : sp a p p l i c a t i o n / o c
0000100 t e t - s t r e a m ; sp c h a r
0000120 s e t = b i n a r y cr nl T r a n
0000140 s f e r - E n c o d i n g : sp c
0000160 h u n k e d cr nl cr nl 1 cr nl a cr nl
0000200
➜ nc -l 8000 < chunked.txt
Open localhost:8000 in Firefox
Hit CTRL+C in terminal
Chrome responds ERR_INCOMPLETE_CHUNKED_ENCODING, Firefox starts downloading and marks download as Completed
Updated•2 years ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Comment 9•9 months ago
|
||
I tried to reproduce again, but nowadays we raise the error NS_ERROR_NET_PARTIAL_TRANSFER
on the channel. The download is marked as failed as well. After doing some digging, it got probably fixed with Bug 1531344. Closing as duplicate of that.
One-line test server in bash: while [ 1 ]; do printf 'HTTP/1.1 200 OK\r\nConnection: close\r\nContent-Type: application/octet-stream; charset=binary\r\nTransfer-Encoding: chunked\r\n\r\n1\r\na\r\n' | nc -Nl 8000; done
Description
•