There was some suggestion that .htaccess would get hit at the end of the
> request chain, and that this might work...
>
> RewriteRule .* - [E=AJP_KRB5CCNAME:%{KRB5CCNAME}]
>
>
Ok.. so that didn't work in .htaccess, but this did..
RewriteRule .* - [E=AJP_KRB5CCNAME:%{ENV:KRB5CCNAME}]
Putting it in .htaccess won't work, though, because the request needs to be
proxied through mod_proxy_ajp.
Fromt the mod_rewrite docs..
http://httpd.apache.org/docs/current/mod/mod_rewrite.html
- On the other hand, because mod_rewrite implements its per-directory
context (.htaccess file) via the Fixup phase of the API and because the
authorization phases come *before* this phase, you just can use
%{REMOTE_USER} in that context.
So... I'm guessing this is working because cosign is running before
mod_rewrite in this configuration.
Based on the description, it seems like the lookahead options should let me
get around this..
- %{LA-U:variable} can be used for look-aheads which perform an internal
(URL-based) sub-request to determine the final value of *variable*. This
can be used to access variable for rewriting which is not available at the
current stage, but will be set in a later phase.
Neither LA-U or LA-F is working.
I've tried the httpd.conf, virtualhost, directory and location contexts. I
don't even see the variable I'm trying to populate in the httpd.conf or
directory contexts. In the virtualhost and location context, the
variables created by rewrite are present, but only the one based on
REMOTE_USER has value. The rest are null.
Cosign is enabled at the server root for this virtual host.
Liam
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Cosign-discuss mailing list
Cosign-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
