Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upnet/http: ServeContent does not send Content-Range in 416 errors #15798
Comments
quentinmit
changed the title
http.ServeContent does not send Content-Range in 416 errors
net/http: ServeContent does not send Content-Range in 416 errors
Jun 17, 2016
quentinmit
added
the
NeedsFix
label
Jun 17, 2016
quentinmit
added this to the Go1.8 milestone
Jun 17, 2016
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Sure, seems like a failure mode we overlooked in the implementation. Also seems like low hanging fruit for anyone looking for something to do. |
adg
added
the
help wanted
label
Jun 17, 2016
This comment has been minimized.
This comment has been minimized.
gopherbot
commented
Jun 17, 2016
|
CL https://golang.org/cl/24212 mentions this issue. |
gopherbot
closed this
in
aa9b3d7
Aug 25, 2016
golang
locked and limited conversation to collaborators
Aug 25, 2017
gopherbot
added
the
FrozenDueToAge
label
Aug 25, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
anacrolix commentedMay 23, 2016
https://tools.ietf.org/html/rfc7233#section-4.4 says that if the range cannot be satisfied because it is beyond the length of the instance, Content-Range should be returned with a 416 containing the instance length. This does not occur with http.ServeContent.