Re: [EMAIL PROTECTED] question on port number from client to host

That's how it works. Outgoing HTTP requests bind to a random unused, unprivileged port on the client machine and connect to port 80 on your server. A different outgoing port will be used on subsequent requests. Mike On Thu, Jul 17, 2008 at 9:24 PM, RCKV <[EMAIL PROTECTED]> wrote: > hello > > I

Re: [EMAIL PROTECTED] PATH_INFO and SCRIPT_NAME for handlers at root level

Thanks, Torsten. It looks like that approach will work perfectly for what I need. Mike On Sat, Jul 12, 2008 at 10:26 AM, Torsten Foertsch <[EMAIL PROTECTED]> wrote: > On Fri 11 Jul 2008, Mike Friedman wrote: >> I've got a mod_perl handler setup lik

[EMAIL PROTECTED] PATH_INFO and SCRIPT_NAME for handlers at root level

Greetings! I'm using Apache 2.2.4 with mod_perl 2.0.3. I've got a mod_perl handler setup like so, within a vhost: SetHandler perl-script PerlResponseHandler MyApp::Dispatcher Under this setup, if I navigate to /myapp/foo/bar/baz, I get: PATH_INFO => /foo/bar/baz SCRIPT_NAME =