Jan Algermissen wrote:
Hi,
I am working on an implementation of a notification system based on HTTP
and I need to write a mod_perl-based Apache module that handles the
(non-HTTP1.1 MONITOR method).
I started using the URI translation phase which works fine, but since I
need support for virtual hosts and per-directory configuration, I'd
rather like to use the header parse phase.
Unfortunately, Apache seems to complain about the unknown HTTP method
right inside the URI translation phase and thus doesn't even reach
the header parse phase but sends a 501 right away.
Can anyone provide me with a hint how to work around this or what
I am doing wrong?
[I am thinking about using the post-read-request phase to change the
method to GET and using a variable to tell the header-parse phase
that the method has actually been a MONITOR. Does that make sense?]
Many thanks in advance!
Under mp2 it's trivial:
http://perl.apache.org/docs/2.0/user/handlers/http.html#Extending_HTTP_Protocol
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
