[Bug 53602] Support for HTTP status code 451

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=53602

Sattarmenu  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #9 from Sattarmenu  ---
hey.
I had just read your content and find very informative knowledge from this
article.
we have a game website where you can get the game of real money winning which
name is https://sattamatka4result.in/;>  
you will find an amazing interface to play all the games.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=53602

Mark Thomas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED

--- Comment #8 from Mark Thomas  ---
Fixed in:
- trunk for 9.0.0.M16 onwards
- 8.5.x for 8.5.10 onwards
- 8.0.x for 8.0.40 onwards
- 7.0.x for 7.0.74 onwards

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

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 include an explanation, in
   the response body, of the details of the legal demand: the party
   making it, the applicable legislation or regulation, and what classes
   of person and resource it applies to.  For example:

   HTTP/1.1 451 Unavailable For Legal Reasons
   Link: ; rel="blocked-by"
   Content-Type: text/html

   
Unavailable For Legal Reasons

 Unavailable For Legal Reasons
 This request may not be serviced in the Roman Province
 of Judea due to the Lex Julia Majestatis, which disallows
 access to resources hosted on servers deemed to be
 operated by the People's Front of Judea.

   


And furthermore:

   As noted above, when an attempt to access a resource fails with
   status 451, the entity blocking access might or might not be the
   origin server.  There are a variety of entities in the resource-
   access path which could choose to deny access, for example ISPs,
   cache providers, and DNS servers.

   It is useful, when legal blockages occur, to be able to identify the
   entities actually implementing the blocking.

   When an entity blocks access to a resource and returns status 451, it
   SHOULD include a "Link" HTTP header field [RFC5988] whose value is a
   URI reference [RFC3986] identifying itself.  When used for this
   purpose, the "Link" header field MUST have a "rel" parameter whose
   value is "blocked-by".

   The intent is that the header be used to identify the entity actually
   implementing blockage, not any other entity mandating it.  A human
   readable response body, as discussed above, is the appropriate
   location for discussion of administrative and policy issues.

Just in case anyone is interested in more support than simply adding status
code and reason phrase.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=53602

Konstantin Kolinko  changed:

   What|Removed |Added

   Target Milestone|--- |-
Version|trunk   |unspecified
 Resolution|LATER   |---
Product|Tomcat 7|Tomcat 9
  Component|Catalina|Catalina
 Status|RESOLVED|REOPENED

--- Comment #6 from Konstantin Kolinko  ---
Changing from RESOLVED LATER to REOPENED
and moving from Tomcat 7 to Tomcat 9.

(In reply to Konstantin Kolinko from comment #1)
> I do not mind adding the new status code, but the comment in the
> LocalStrings.properties file says that the codes come from IANA page,
> http://www.iana.org/assignments/http-status-codes/http-status-codes.xml
> 
> Either a comment should be added on where the code comes from, or we can
> wait until a proper RFC is issued and IANA page is updated with the new code.

The IANA page has been updated and now lists the code 451 as assigned and links
to the following draft.

The draft linked from IANA page has a different name,
https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/

Its History page says that it has been approved on 2015-12-21.

Apparently it has not been published as an RFC yet, but it is going to become
one.


A blog post and Wikipedia:
https://www.mnot.net/blog/2015/12/18/451
https://en.wikipedia.org/wiki/HTTP_451

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

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 code, eh?) with a response
message can manually set the message until such time as Tomcat supports it (due
to standards approval).

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

https://issues.apache.org/bugzilla/show_bug.cgi?id=53602

Mark Thomas ma...@apache.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |LATER

--- Comment #4 from Mark Thomas ma...@apache.org ---
This (and any other new codes) can be added once they are approved.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

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 because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

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://datatracker.ietf.org/doc/draft-tbray-http-legally-restricted-status/history/

The current version of the document is 01.


I do not mind adding the new status code, but the comment in the
LocalStrings.properties file says that the codes come from IANA page,
http://www.iana.org/assignments/http-status-codes/http-status-codes.xml

Either a comment should be added on where the code comes from, or we can wait
until a proper RFC is issued and IANA page is updated with the new code.

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

[Bug 53602] Support for HTTP status code 451

[bugzilla]

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 adjust that comment as you see fit.

There are two places with HTTP status codes:

tomcat/trunk/java/org/apache/catalina/valves/LocalStrings.properties
tomcat/trunk/java/org/apache/tomcat/util/http/res/LocalStrings.properties

You might want to add the new one to the other list as well.

Regards,

Rainer

-- 
You are receiving this mail because:
You are the assignee for the bug.

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org