> I wouldn't really call this a modperl question but regardless...
Sorry if this was off topic. I subscribed to this list a few months ago
for another issue and have seen a number of posts dealing with
mod_rewrite. I'll be mindful in the future.
Chris
Thanks Rob, this might be it.
As we can't expect our users to know to use "%2B" instead of "+", we'll
try replacing it in the rewrite.
Chris
-Original Message-
From: Robert Landrum [mailto:[EMAIL PROTECTED]
Sent: Monday, December 18, 2006 11:01 AM
To: Chris Schults
Cc: modperl@perl.apac
I wouldn't really call this a modperl question but regardless...
Chris Schults wrote:
It appears that the "+" is getting stripped out at some point as the
script is returning results for "water pollution" instead of
"water+pollution". Is it possible that Apache is the culprit or should
we be loo
Chris Schults wrote:
It appears that the "+" is getting stripped out at some point as the
script is returning results for "water pollution" instead of
"water+pollution". Is it possible that Apache is the culprit or should
we be looking more closely at our script or rewrite rule?
The test would
We have a CGI script that will list all the stories tagged with a
specified keyword. For example, if you wanted to see all stories tagged
with "pollution":
/cgi-bin/script.pl?query=gristkeywords=pollution
For a more user-friendly URL, we setup the following rewrite rule in an
.htaccess file that
Alan R Williamson wrote:
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to do it.
oooh its blank. i take it thats not good!
That means you've been running these scripts through mod_cgi, not
mod_p
Perrin Harkins wrote:
Alan R Williamson wrote:
When i hit the .cgi pages, with perl in them, they run fine, so perl
is definitely being triggered.
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to
Alan R Williamson wrote:
When i hit the .cgi pages, with perl in them, they run fine, so perl is
definitely being triggered.
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to do it.
- Perrin
Yes, that should be one of the first ( if not the first ) log message
you see on server startup.
Have you tried running this with a single Apache process ( -X ) to
see if you get different results?
Yes, i tried that, and it didn't make any difference.
When i hit the .cgi pages,
On Mon, 18 Dec 2006 15:35:54 +
Alan R Williamson <[EMAIL PROTECTED]> wrote:
> Still struggling with this sadly.
>
> Frank, i tried what you said, but still no different.
>
> however, when i shutdown Apache i get this:
> _
>
> XAMMP: Stopping Apach
Still struggling with this sadly.
Frank, i tried what you said, but still no different.
however, when i shutdown Apache i get this:
_
XAMMP: Stopping Apache
[notice] Apache:DB initialized in child 32021
_
11 matches
Mail list logo
