[for the archive]
I wrote:
> I have intermittent segmentation faults with Apache 1.3.14, mod_perl
> version 1.24. I think I tracked the problem down to the Frontier::RPC2
> module, which uses XML::Parser.
The problem has been fixed - the culprit was the version of XML::Parser/
expat I was using
From: Chris Lott <[EMAIL PROTECTED]>
> Been using and liking ActiveState perl. Used ppm install to install the
> latest mod_perl for Apache 1.3.20 (from . PPM ran fine, the module appeared
> where it was supposed to, but in the documentation for enabling it in the
> httpd.conf it refers to a "sta
Hi,
I have intermittent segmentation faults with Apache 1.3.14, mod_perl
version 1.24. I think I tracked the problem down to the Frontier::RPC2
module, which uses XML::Parser. I've seen a few postings in the archives
about problems with mod_perl and certain versions of XML::Parser, so
that's my b
Hi,
a friend suggested I crosspost this here, in case there are some people
on this list (like me) who are not subscribed to [EMAIL PROTECTED],
and this might be interesting to the mod_perl community as well. I'd
like to thank the ASF security staff for their good work and the
comprehensive ex
From: <[EMAIL PROTECTED]>
> any Proxy operator can do this with any non-SSL connection. One can spy session
> ids in the URL, in the GET-parameters and the POST-parameters, also cookies and
> basic auth passwords, also passwords in html forms - and every bit of data
> that's send back.
>
> Oh, a
From: <[EMAIL PROTECTED]>
> A better way for session ids is to put them in front of the URI:
> http://www.nus.edu.sg/dfd3453/some/path/and/file.html
(...)
> These session ids are sticky as long as you only use relative paths in your
> html. Note: You may want to put your images in a directory tha
