[modperl 1.27] Problem regarding Perl*Handler and the HTTP request line

Hi all Apologise if I have posted to the wrong list. I am quite new to the Perl*Handlers. Iam wondering if it is possibleto write a handler which parses the very first header line, say.. telnet localhost http Trying 127.0.0.1 Connected to localhost. Escape character is '^]' [C]

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequest line

On Tue, 24 Dec 2002 [EMAIL PROTECTED] wrote: Hi all Apologise if I have posted to the wrong list. I am quite new to the Perl*Handlers. I am wondering if it is possible to write a handler which parses the very first header line, say.. telnet localhost http Trying 127.0.0.1 Connected

[OT] Season's Greetings

Just a quick note to wish you all a Merry Christmas and all the best for 2003. I would like to thank everyone on the list for all the help and support you have given me over the past year. You have my sincere appreciation. -- Jonathan M. Hollin Technical Director: Digital-Word Co.

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequest line

On Tue, 24 Dec 2002 [EMAIL PROTECTED] wrote: I am wondering if it is possible to write a handler which parses the very first header line, say.. No, it's not possible. (Unless I'm really missing something) where the line followed by [C] stands for the line sent by the client, and the

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequest line

where the line followed by [C] stands for the line sent by the client, and the line followed by [S] is the line sent by some perl module. It sounds to me as though you want to use Apache as a network service framework. Not a bad idea, but Apache already stands on a set protocol. Is this

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequest line

From: [EMAIL PROTECTED] In fact I would like to write some little scripts to talk with the internals of Apache over port 80... By the internals, do you mean asking Apache about what it's doing and sending it new directives? If all you need to do is catch particular requests, then Nick

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequestline

I was wondering if it is possible to write a handler to handle a 'new http method', because I could not find any hint in the user guide. :) if my 'new http method' you mean something other that GET, POST, PUT, etc then no, you cannot (in Apache 1.3, at least). just about the only thing you

RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun doesn't work?

I have searched the archives and various websites to find my problem and its associated resolution to no avail. I upgraded my working Apache 1.3 and mod_perl 1.x website using the PerlRun option of modperl to the RedHat 8.0 standard release with Apache/mod_perl 2.0 combo -- bad move it

Re: RedHat 8.0 standard Apache2.0 and mod_perl 2.0::PerlRun doesn'twork?

Dale Lancaster wrote: I have searched the archives and various websites to find my problem and its associated resolution to no avail. I upgraded my working Apache 1.3 and mod_perl 1.x website using the PerlRun option of modperl to the RedHat 8.0 standard release with Apache/mod_perl 2.0

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequest line

if my 'new http method' you mean something other that GET, POST, PUT, etc then no, you cannot (in Apache 1.3, at least). yea. you got exactly what I mean!! :D I want to put this non HTTP thing together with some other Apache::Registry scripts on the same port 80 with modperl 1.27 and Apache

Re: [modperl 1.27] Problem regarding Perl*Handler and the HTTPrequestline

in Apache/mod_perl 2.0, you can write an input filter that _does_ allow you do parse the Request Line yourself. then again, you can write a protocol handler for any protocol you can dream up, so there's no reason to mess with HTTP :) Actually in 2.0 you can even implement this in a

mod_perl php apache || !

Recently I gave php a go. While playing with it I was unable to find any documentation pertaining to how it interacts with apache (e.g. php provides some nice session functions and cookie handling, but doesn't explain at exactly which phases of the apache request loop it's interacting with

Relative path problem

I installed the Win32 mod_perl 1.0 in Windows XP Professional just to see how it works. This distribution contains Perl 5.6.1 and Apache_1.3.27, together with mod_perl-1.27. In my index.pl, I call another perl file using a reletive path, like ../lib/work.pm. But I found this file cannot be

RE: mod_perl php apache || !

Hi - While converting a site to mod_perl/mason from php, I had varying degrees of the site using php and mod_perl with no problems. I think you would be safe. But remenber Perl Rules! and mod_perl rocks! :) Aloha = Beau. -Original Message- From: Joseph P. Crotty [mailto:[EMAIL

cvs commit: modperl Changes

stas2002/12/24 17:46:10 Modified:src/modules/perl perl_util.c .Changes Log: prevent segfaults in mod_perl_mark_where() when a sub can't get resolved Submitted by: Gerald Richter [EMAIL PROTECTED] Reviewed by: stas Revision ChangesPath