"Alexei V. Barantsev" wrote:
>
> Hello, All!
>
> I have the followin problem: HTML::Mason dhandler could not define
> path_info, it tries to select only first part. For example, if my
> request is http://server/test/hello/world and dhandler is in /test
> it decides that $r->path_info is /hello/.
Doug MacEachern wrote:
> what options did you give mod_perl's Makefile.PL?
perl Makefile.PL \
APACHE_PREFIX=/usr/local/apache/ \
APACHE_SRC=/usr/local/apache/src\
DO_HTTPD=1 \
USE_APACI=1 \
APACI_ARGS='--enable-module=rewrite --enable-module=so
--enable-module=proxy' \
I've written an access handler which takes some custom configuration
directives based on the instructions in chaper 8 of the Eagle book.
Everything makes and installs fine, and I am able to load the module
with a PerlModule directive, but when I try to use the directives
defined in my module I g
"J. Horner" wrote:
> "It is called once per transaction and is intended to allow modules to
> step in and perform special processing on the incoming data", which is
> what I want, but it goes on to say, "However, because there's no way for
> modules to step in and actually contribute to the parsin
Ilya Obshadko wrote:
>
> Hello,
>
> I've discovered the following. Suggest that you use Apache::Request
> object in both fixup handler and registry script. So we have:
>
> 1) unpredictable segmentation faults
I had the same problem. I think there must be some problems in libapreq
(whic
I'm getting occasional segfaults when calling the $r->pnotes()
method.
There are no errors in the error log, until I get a line like this:
[Sat Feb 5 19:36:58 2000] [notice] child pid 19989 exit signal
Segmentation fault (11), possible coredump in /backend/scratch
(I ran the mod_perl server on
I'm attempting to use the byteserving methods of Apache::File, but I'm
getting strange results. Apache 1.3.9, mod_perl 1.21.
Here's the request (entered via telnet to port 80):
GET /image/1000/foo.gif HTTP/1.1
Host: www.eorbit.net
Range: bytes=0-50
Here's a code snippet:
.
.
.
unless ($r->he
Atipat Rojnuckarin wrote:
>
> Hi,
>
> If /image/1000/foo.gif does not map to an actual file
> on the server, you will need to have content length
> set for set_byterange to work. Otherwise, check out
> the C source for ap_set_byterange in http_protocol.c
> (in Apache distribution).
>
> dak
Tha