https://bz.apache.org/bugzilla/show_bug.cgi?id=53602
Sattarmenu changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #9 from Sattarmenu
https://bz.apache.org/bugzilla/show_bug.cgi?id=53602
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
https://bz.apache.org/bugzilla/show_bug.cgi?id=53602
--- Comment #7 from Rainer Jung ---
Additional info. The RFC draft
https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/?include_text=1
says:
Responses using this status code SHOULD
https://bz.apache.org/bugzilla/show_bug.cgi?id=53602
Konstantin Kolinko changed:
What|Removed |Added
Target Milestone|--- |-
https://issues.apache.org/bugzilla/show_bug.cgi?id=53602
--- Comment #5 from Christopher Schultz ch...@christopherschultz.net ---
(In reply to Mark Thomas from comment #4)
This (and any other new codes) can be added once they are approved.
+1
Any webapp that wants to use code 451 (amusing
https://issues.apache.org/bugzilla/show_bug.cgi?id=53602
Mark Thomas ma...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=53602
--- Comment #3 from Julian Reschke julian.resc...@gmx.de ---
Wait.
Why add a status code that hasn't been approved yet?
The spec might go nowhere. Or it might be approved, but with a different status
code.
--
You are receiving this mail
https://issues.apache.org/bugzilla/show_bug.cgi?id=53602
--- Comment #1 from Konstantin Kolinko knst.koli...@gmail.com ---
Link to versions of the proposal to add this new status code to HTTP
in IETF document tracking tool:
https://issues.apache.org/bugzilla/show_bug.cgi?id=53602
--- Comment #2 from Rainer Jung rainer.j...@kippdata.de ---
OK to add for me. The IANA link I added to the comments wasn't meant to police
other status code additions but instead to be useful for future checks. So Tim,
you might want to