RE: [users@httpd] Odd interaction between mod-rewrite and mod-cgi

2005-07-11 Thread Axel-Stéphane SMORGRAV
The lines you describe as "additional output" are actually perfectly normal HTTP response headers. I suggest you take a peek at the response stream using HTTP Watch or a sniffer to look for a clue as to why those lines appear in the browser. -ascs -Original Message- From: Sean Conner [

Re: [users@httpd] Odd interaction between mod-rewrite and mod-cgi

2005-07-10 Thread Sean Conner
It was thus said that the Great Joshua Slive once stated: > > On 7/9/05, Sean Conner <[EMAIL PROTECTED]> wrote: > > > RewriteRule ^([0-9][0-9])(.*) nph-blog.cgi/$1$2 [L] > > RewriteRule ^(test)(.*) nph-raw.cgi/$1$2 [L] > > RewriteRule ^(foo)(.*)nph-raw

Re: [users@httpd] Odd interaction between mod-rewrite and mod-cgi

2005-07-10 Thread Joshua Slive
On 7/9/05, Sean Conner <[EMAIL PROTECTED]> wrote: > RewriteRule ^([0-9][0-9])(.*) nph-blog.cgi/$1$2 [L] > RewriteRule ^(test)(.*) nph-raw.cgi/$1$2 [L] > RewriteRule ^(foo)(.*)nph-raw.cgi?$1$2 [L] > > Hit the following URLs: > > http://work.

[users@httpd] Odd interaction between mod-rewrite and mod-cgi

2005-07-09 Thread Sean Conner
I have a few CGI scripts, written in C (legacy stuff that I don't wish to rewrite if possible) that work fine under Apache 1.3. When moved to Apache 2.0.54 (latest version) they still work, but Apache seems to include additional output at the bottom of the page: HTTP/1.1 200 OK Date: S