Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
net/http: StatusText(416) returns "Requested Range Not Satisfiable" should be "Range Not Satisfiable" #42276
RFC 7233 defines 416 as "Range Not Satisfiable". This was previously "Requested Range Not Satisfiable" in RFC 2616, which is obsolete.
But everywhere this occurs, whether it's user code calling
And yes, I realize this is the minorest of issues.
What version of Go are you using (
Thank you for this question @rob05c and welcome to the Go project!
So firstly we've had this status message for the past 11+ years without a complaint. RFC 7233 was made in 2014 aka >6 years ago.
Data from survey
To survey prominent infrastructure on the internet to see if we've deviated, or perhaps as motivation for if we should change it, backed by data on what others have done:
Of the 14 surveyed popular/critical internet infrastructure, only 3 use that newer RFC's definition -> 21.43%
Given that that might be a sudden change that hasn't been propagated to majority of the surveyed infrastructure as per above, I don't think we should make this change. Despite it being low-risk and not necessarily under the Go1 compatibility promise as it is a status message so amenable, by Hyrum's law, a change (moreover after 11+ years) is bound to break code for someone, and no report has come in in the past 6+ years since its introduction. I thus vote to say let's not change this, but definitely a consideration for Go2, which will give enough time perhaps for maturity of that RFC and adoption by others too.