[jira] [Resolved] (TS-1890) authproxy plugin caching and reliability fixes

["James Peach (JIRA)" <ji...@apache.org>]

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

James Peach resolved TS-1890.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.3.3
         Assignee: James Peach

commit 07466943bdda4ac4d4f4b8e0ea3f145f5ae1feaf
Author: James Peach <jp...@apache.org>
Date:   Thu May 9 15:18:29 2013 -0700

                
> authproxy plugin caching and reliability fixes
> ----------------------------------------------
>
>                 Key: TS-1890
>                 URL: https://issues.apache.org/jira/browse/TS-1890
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Plugins
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 3.3.3
>
>
> While doing some testing on an authproxy deployment, we needed to make a couple of fixes.
> Make sure that the requests to the authentication proxy are never cached. We must not accidentally use stale authentication information.
>     
> Add special handling for Content-Length when authorizing HEAD requests. We should not force the length to zero in this case because the client knows that HEAD responses must always have an empty body. This is really a workaround for a buggy client, hdiutil(1) on Mac OS X.

--
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