On Thu, Oct 3, 2013 at 1:06 AM, Chris Darroch chr...@pearsoncmg.com wrote:
Chris Darroch wrote:
The intent of r1357986 was to deal with a particular, wonky
sub-case, when the Authorizer returns 200 (so the spec paragraph
doesn't apply in this case, as it's a 200 OK response), but adds
a
Jeff Trawick wrote:
The app is out of spec either way. I think the trunk behavior is better.
I'd agree on both counts (the latter IMHO, of course). For reference,
here's a breakdown of 2.3.7 vs. trunk behaviour for Authorizers:
Authorizer response2.3.7
Jeff Trawick wrote:
URL: http://svn.apache.org/viewvc?rev=1357986view=rev
http://svn.apache.org/viewvc?rev=1357986view=rev
Log:
Avoid internal sub-requests and processing of Location headers when
in FCGI_AUTHORIZER mode, as the mod_fcgid_authenticator(), etc. hook
Chris Darroch wrote:
The intent of r1357986 was to deal with a particular, wonky
sub-case, when the Authorizer returns 200 (so the spec paragraph
doesn't apply in this case, as it's a 200 OK response), but adds
a Location header with a relative (not absolute) path. In this case,
2.3.7 and
On Thu, Jul 5, 2012 at 7:01 PM, chr...@apache.org wrote:
Author: chrisd
Date: Thu Jul 5 23:01:09 2012
New Revision: 1357986
URL: http://svn.apache.org/viewvc?rev=1357986view=rev
Log:
Avoid internal sub-requests and processing of Location headers when
in FCGI_AUTHORIZER mode, as the
