Hello everybody,
I'm wondering how CAP::apache affects CAP::*, such as CAP::Session.
[snip location=http://search.cpan.org/~wonko/CGI-Application-Plugin-
Apache-0.09/lib/CGI/Application/Plugin/Apache.pm] Override the way
CGI::Application creates and prints it's HTTP headers [/snip]
Am I right
Tarek W. wrote:
Hello everybody,
I'm wondering how CAP::apache affects CAP::*, such as CAP::Session.
[snip location=http://search.cpan.org/~wonko/CGI-Application-Plugin-
Apache-0.09/lib/CGI/Application/Plugin/Apache.pm] Override the way
CGI::Application creates and prints it's HTTP headers [/snip]
On Sun, 05 Dec 2004 17:50:53 -0500, Michael Peters
[EMAIL PROTECTED] wrote:
Tarek W. wrote:
Hello everybody,
I'm wondering how CAP::apache affects CAP::*, such as CAP::Session.
[snip location=http://search.cpan.org/~wonko/CGI-Application-Plugin-
Cees Hek wrote:
On Sun, 05 Dec 2004 17:50:53 -0500, Michael Peters
[EMAIL PROTECTED] wrote:
Right now they are incompatible. This is not because of the way
CAP::Apache deals with http headers but because CAP::Session assumes
your query object has a 'cookie()' method.
You can still use both