OK, light finally dawned over marblehead so to speak...
There is an unfortunate interaction between the new Session plugin and XSL
params. The issue is that if a cookie has a name containing colons in it, it
cannot be turned legally into a corresponding request.cookie.<cookiename> XSL
parameter. The new Session plugin did exactly that, which caused the somewhat
mysterious seeming crash when AxKit tried to process the XSL after the
parameter was added...
I'm not 100% sure what the perfect solution is, but the following hack to the
Apache::AxKit::Plugin::AddXSLParams::Request module does fix the problem by
stripping the colons out of the cookie name before its passed to XSL.
Hope this is useful to you guys :o).
25d24
< #warn "Parsed Cookies\n";
27,30c26
< my $foofoo = $oreo;
< $foofoo =~ s/\://g;
< $cgi->parms->set('request.cookie.' . $foofoo =>
$cookies->{$oreo}->value );
< #warn "Setting header for cookie $oreo\n";
---
> $cgi->parms->set('request.cookie.' . $oreo =>
$cookies->{$oreo}->value );
36d31
< #warn "Done with cookies\n";
37a33
>
64d59
< #warn "Finished with AddXSLParams\n";
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
