[snip]
Also, I hate to whine, but despite the docs saying so, whatever value my
script returns is completely ignored; I have to use $R-status (). I'm
using Apache::Registry, in case that makes any difference.
Apache::Registry ignores the actual return code from your script,
using instead the
Geoffrey Young wrote:
[snip]
Also, I hate to whine, but despite the docs saying so, whatever value
my script returns is completely ignored; I have to use $R-status ().
I'm using Apache::Registry, in case that makes any difference.
if some online documentation says otherwise, please let us
The doc on issuing correct http headers has returns with values all over
it:
http://perl.apache.org/docs/general/correct_headers/correct_headers.html
the examples in that document assume that you're using mod_perl
handlers, not Apache::Registry, though I admit that's not obvious
unless you
DeAngelo:
I have not heard any reply to this email. We currently build
mod_perl 1.27 for SGI IRIX64 using standard techniques and do
*not* experience any build problem. If you send me the output
of the par command I may be able to help you pinpoint your
problem.
Thanks
Paul E Wilt
Senior
* Cristvo Dalla Costa [EMAIL PROTECTED] [2002-10-25 20:29]:
Hi, I'm trying to get my script to work with conditional get, however,
when the browser should use the local copy it doesn't display
anything, just telling me that the image's broken.
The Eagle book implies that you need to use
I have some troubles with mod_perl (loosing indata), but the problems are so
obscure that it seems to me as I am the only (or one of very very few) who are
encountering these problems.
Anyway, what I need to continue finding this problem and eliminating it is:
Where is the C code to mod_perl
At 15:47 28.10.2002, =?UTF-8?B?Q3Jpc3TDs3bDo28gRGFsbGEgQ29zdGE=?= wrote:
Geoffrey Young wrote:
[snip]
Also, I hate to whine, but despite the docs saying so, whatever value
my script returns is completely ignored; I have to use $R-status ().
I'm using Apache::Registry, in case that makes any
RK But this doesn't seem to be the problem ... What's printed in the
RK browser? Is there anything in the error logs? Is the name of the
RK directory to be read input from the user (if so, are you running
RK under taint mode?), and are the permissions appropriate?
Here is my module's code...
use
Anders Lidén wrote:
I have some troubles with mod_perl (loosing indata), but the problems are so
obscure that it seems to me as I am the only (or one of very very few) who are
encountering these problems.
Anyway, what I need to continue finding this problem and eliminating it is:
Where is
Apparently some of the compile options need to be delimited by commas for compilers on
SGI IRIX64 system.
For a quick refresher on what the error was, the following error shows up during the
Makefile.PL run:
ld32: FATAL 9: I/O error (1110): No such file or directory
The way to get rid of
Richard Clarke wrote:
Before I embark on a day exploring the pros and cons of today's
cleaning/compression tools, I wondered if any of you could give me some
feedback about your own experiences within the context of medium/large scale
web sites/applications (E-Toys etc).
We didn't use
Thank you for your help!
I'm terribly sorry for getting your time, It's my fault.
There was an error in my code.
I'm inattentive foolish man.
But I've known new methods of reading directory listening.
Best regards.
___
Sorry for my English.
DeAngelo:
Your sysadmin sure has a good eye! The link that you pointed to earlier:
http://www.mail-archive.com/modperl;apache.org/msg28889.html
has the following lines in it:
Error Output for sanity check
cd ..; cc -n32 -DIRIX -DMOD_PERL
DeAngelo:
Quick follow-up! I looked in our setups and found that we
actually use the LFLAGS (versus the CFLAGS) variable to pass
this information to the linker. Try uncommenting the change
you made and set the LFLAGS (ours has -g -n32 -mips4 -Wl,-woff,84) and
see if that works. If so then we
Walt,
I changed the PERL_EXTRA_CFLAGS variable in Makefile.PL to LFLAGS and got the
following error:
don't know how to make lib/Apache/MyConfig.pm (bu42).
Also, there was no LFLAGS variable in the orginal generated Makefile. There are a
couple variables called LDDLFLAGS and CCCDLFLAGS which
So, try the following change to your code:
$R-content_type ($data {mimetype});
$R-set_content_length ($data {size});
$R-header_out ('ETag',$data {md5});
don't do that. use the $r-set_etag method instead, which is probably
a bit safer than trying to figure out Etag rules
Gurus,
I have compiled mod_perl 1.27 with apache 1.3.27 under perl 5.8.0, solaris
2.6, using gcc 2.7.2.3. When I run the make test, it fails with the
following in the error_log:
/usr/local/bin/perl5.8.0 t/TEST 0
modules/actions...ok
modules/cgi...FAILED test 4
Failed
On Sun, 27 Oct 2002, Richard Clarke wrote:
Before I embark on a day exploring the pros and cons of today's
cleaning/compression tools, I wondered if any of you could give me some
feedback about your own experiences within the context of medium/large scale
web sites/applications (E-Toys
Steve,
I have no objection to replying to the mod_perl list. I have no idea what is wrong
I am so new at all of this that the more people who might have an idea the better.
I am running Apache 1.3.22 and mod_perl 1.21 on a Sun Solaris 2.6 machine. I'm sure
Apache and mod_perl are
I have compiled mod_perl 1.27 with apache 1.3.27 under perl 5.8.0,
solaris 2.6, using gcc 2.7.2.3. When I run the make test, it fails
Did you build your Perl 5.8.0? I ask because the general advice is
that the same compiler must build both Perl and mod_perl. Some people
seem to have had
Do you have multiple versions of perl installed?
Try a clean installation of perl and use the same
compiler and same flags in building everything.
Regards,
Jie
On Mon, 28 Oct 2002, John E. Mendenhall wrote:
Date: Mon, 28 Oct 2002 12:44:07 -0800 (PST)
From: John E. Mendenhall [EMAIL
> ... I am so new at all of this that the more people who might have
an idea the better.
We've all had to start somewhere. The spirit of open source is global
support.
Perhaps you might like to check the following from the mod_perl user
guide.
It sounds like mod_perl is installed and running OK. Quoting from
http://httpd.apache.org/docs/mod/core.html#limit:
In the general case, access control directives
should not be placed within a limit section.
Do you need the limit section? Can you run without it?
Steve
Mitchel,
Hi there,
On Mon, 28 Oct 2002, John E. Mendenhall wrote:
I have compiled mod_perl 1.27 with apache 1.3.27 under perl 5.8.0,
solaris 2.6, using gcc 2.7.2.3. When I run the make test, it fails
Did you build your Perl 5.8.0? I ask because the general advice is
that the same compiler must build
24 matches
Mail list logo
