> No, they shouldn't! PATH_INFO '... holds the additional path > information > that remains after the URI has been translated into a file path.' [1] > So, if your URI is 'http://site/test2.html' > > 1) URI to file translation: > > http://site/test2.html => {DOCUMENT ROOT}/test2.html > > 2) All of the URI is used for the file translation, no path > information is > left.
That's the main request. #include is supposed to perform an internal sub-request for the new URL, with the environment setup accordingly. If I wanted the *original* query string and path_info I would be using #exec-cgi rather than #include virtual. The second section of this email : http://www.mail-archive.com/dev@httpd.apache.org/msg17597.html on the apache-dev mailing list, suggests that what I've tested should work. Carl -------------------------------------------------------- GMG Regional Digital is part of the Guardian Media Group plc. CONFIDENTIALITY NOTICE. The information contained in this e-mail is intended only for [EMAIL PROTECTED], [EMAIL PROTECTED] It may contain privileged and confidential information that is exempt from disclosure by law and if you are not an intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this e-mail in error, you may notify our helpdesk by telephone on 44 (0)161 211 2222. E-mail transmission cannot be guaranteed to be secure or error-free. The sender ([EMAIL PROTECTED]) therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
