Daniel Stenberg
2014-04-22 20:21:55 UTC
Hey all,
In the networking team we're about to introduce an error code for "partial
transfers" (see https://bugzilla.mozilla.org/show_bug.cgi?id=237623). It will
be returned when the underlying protocol's framing is cut off and we know that
the transfer was indeed partial - not all data arrived.
Right now the patch in progress returns this value for HTTP 1.1
Content-Length: underrun, cut off chunked-encoding chunks and broken SPDY or
http2 streams.
While the primary bug report for this identifies a problem in the download
manager that makes it not discover cut off transfers and instead signal them
as complete, this change will and can have some further impact on other areas
of Firefox and I want to highlight this, give you all a heads up and listen in
if there are any additional thoughts or feedback on this pending change.
The question I think all consumers of protocol data need to ask ourselves is:
how should we deal with partial contents? Up until today, we silently just
ignored the potential problems and considered whatever we got fine enough to
use. Images? Javascript? CSS? Anything else?
This change will also make Firefox align with the other browsers that already
are stricter in this area.
In the networking team we're about to introduce an error code for "partial
transfers" (see https://bugzilla.mozilla.org/show_bug.cgi?id=237623). It will
be returned when the underlying protocol's framing is cut off and we know that
the transfer was indeed partial - not all data arrived.
Right now the patch in progress returns this value for HTTP 1.1
Content-Length: underrun, cut off chunked-encoding chunks and broken SPDY or
http2 streams.
While the primary bug report for this identifies a problem in the download
manager that makes it not discover cut off transfers and instead signal them
as complete, this change will and can have some further impact on other areas
of Firefox and I want to highlight this, give you all a heads up and listen in
if there are any additional thoughts or feedback on this pending change.
The question I think all consumers of protocol data need to ask ourselves is:
how should we deal with partial contents? Up until today, we silently just
ignored the potential problems and considered whatever we got fine enough to
use. Images? Javascript? CSS? Anything else?
This change will also make Firefox align with the other browsers that already
are stricter in this area.
--
/ daniel.haxx.se
/ daniel.haxx.se