You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/29 08:50:08 UTC

[jira] [Resolved] (SLING-2426) SlingSafeMethodsServlet's default HEAD implementation not completely RFC compliant

     [ https://issues.apache.org/jira/browse/SLING-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-2426.
--------------------------------------

    Resolution: Not A Problem
      Assignee: Felix Meschberger

So I think we can safely resolve this as not being a problem and thus to not do anything about it.
                
> SlingSafeMethodsServlet's default HEAD implementation not completely RFC compliant
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-2426
>                 URL: https://issues.apache.org/jira/browse/SLING-2426
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>    Affects Versions: API 2.2.0
>            Reporter: Boris Pruessmann
>            Assignee: Felix Meschberger
>
> RFC 2616 states: "The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response." 
> The current implementation of the SlingSafeMethodsServlet does not guarantee what's stated above - if the GET call's response gets too big, the servlet engine might switch to chunked transfer. However, the HEAD call returns a valid Content-Length header no matter what, resulting in HEAD returning different headers than the corresponding GET call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira