You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/07/11 19:17:48 UTC

[jira] [Commented] (TS-2024) HTTP Violation: proxies MUST handle 65536byte-long URIs

    [ https://issues.apache.org/jira/browse/TS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705985#comment-13705985 ] 

Leif Hedstrom commented on TS-2024:
-----------------------------------

Note that the way CoAdvisor works, if we were to make ATS handle 64KB long URIs, there's almost certainly going to be a new CoAdvisor test that fails (maybe on 128KB or some such). I'm thinking that the problem here really is that we don't produce a valid (414) error code ?
                
> 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