Arshavir Grigorian wrote:
Geoffrey Young wrote:
libapreq2 is currently using $r->headers_out instead
of $r->err_headers_out, which is why you're not seeing the
cookie on your redirect response. I think the consensus
is that this is a bug in libapreq2-2.04, but I haven't seen
any other apreq commit
Tim Evans wrote:
LoadModule php4_modulelibexec/libphp4.so
LoadModule perl_modulelibexec/libperl.so
Restart apache.
Seg faults on simple test.php page. Error log says (same as before):
[Thu Nov 18 20:48:17 2004] [notice] child pid 22818 exit signal Segmentation
fault (11)
I alw
Geoff Mishkin wrote:
I've got mod_perl (version 1.99.11) all up and running on Apache (version
2.0.52), but the working directory of my scripts is always set to / when
use lib qw(.); # that's a period in between the parens.
--
[EMAIL PROTECTED]
Martin Moss wrote:
However after the rewrite, the POST data is lost. Can
anybody throw any light on this?
the rewrite rule is this:-
RewriteRule ^(.*)$ http://%{HTTP_HOST}$1 [R]
Not sure what you are trying to do here. You are making a non-ssl
request back to the exact same server, with the exact
allen haim wrote:
wget -S gives me:
---
1 HTTP/1.1 200 OK
2 Date: Mon, 18 Apr 2005 15:01:31 GMT
3 Server: Embperl/2.0rc2 Apache/2.0.52 (Unix) mod_perl/1.999.21
Perl/v5.8.5
4 Content-Length: 142
5 Keep-Alive: timeout=15, max=100
6 Connection: Keep-Alive
7 Content-Type: text/html; charset
Scott Cain wrote:
because I had to blow away my installation of mp1 to get my mp2 apps to
work.
I always build my servers with their own copy of perl in a directory
such as:
/usr/local/httpd_20050419
I build a fresh perl and apache in that directory, and get everything
working. My particular
Garrison Hoffman wrote:
I'm storing session IDs in cookies for 60 days, so I'd like to limit
sessions similarly. I could certainly run a cron for this, but is there
a better way?
I believe that deleting them via the cron is the standard method. Test
out the following (by changing rm to l
Michael Hall wrote:
Try simply:
$r->headers_out->set(Location => 'to-URI');
make sure 'to-URI' is absolute and not relative as per the RFC's. I
have had some problems with relative URI's since Apache tends to want to
optimize the call. Instead of sending the 302 headers to the browser,
