[
https://issues.apache.org/jira/browse/TS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Galić updated TS-2024:
---------------------------
Description:
citing the RFC:
{quote}
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
{quote}
Section 3.1.1 of HTTPbis recommends for everyone at least 8k octets:
https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-22#section-3.1.1 -
CoAdvisor "recommends" 65k for proxies.
was:
citing the RFC:
{quote}
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
{quote}
CoAdvisor recommends 65k
> HTTP Violation: proxies MUST handle 65536byte-long URIs
> -------------------------------------------------------
>
> Key: TS-2024
> URL: https://issues.apache.org/jira/browse/TS-2024
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Igor Galić
>
> citing the RFC:
> {quote}
> The HTTP protocol does not place any a priori limit on the length of
> a URI. Servers MUST be able to handle the URI of any resource they
> serve, and SHOULD be able to handle URIs of unbounded length if they
> provide GET-based forms that could generate such URIs. A server
> SHOULD return 414 (Request-URI Too Long) status if a URI is longer
> than the server can handle (see section 10.4.15).
> Note: Servers ought to be cautious about depending on URI lengths
> above 255 bytes, because some older client or proxy
> implementations might not properly support these lengths.
> {quote}
> Section 3.1.1 of HTTPbis recommends for everyone at least 8k octets:
> https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-22#section-3.1.1
> - CoAdvisor "recommends" 65k for proxies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
