This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22386 - fully transmitted
Summary: fully transmitted
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Fetch (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+fetchspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-16 21:28 UTC by Marcos Caceres
Modified: 2013-06-20 05:42 UTC (History)
2 users (show)

See Also:

Attachments

Description Marcos Caceres 2013-06-16 21:28:31 UTC 
In the Fetching section, it speaks of "fully transmitted". Should that be defined or an example given?
Comment 1 Anne 2013-06-19 07:44:47 UTC 
What it means exactly kinda depends on how HTTP is implemented. And that in turn is not very well defined...
Comment 2 Marcos Caceres 2013-06-19 10:56:03 UTC 
Maybe a note would be useful there. However, if you think it's ok, please disregard.