/mod/core.html#acceptmutex). Also, security
errors such as errors from setuid(), setgid(), or getpwuid() may cause a
fatal error. Finally, certain values of errno after the accept() call in
child_main() will cause a fatal error (like ENETDOWN).
--
Kyle Oppenheim
Tellme Networks, Inc.
http
[EMAIL PROTECTED] wrote:
Any plans to make Apache::FakeRequest work well enough to make this
possible?
[EMAIL PROTECTED] wrote:
As for mod_perl 1.0, I'm not sure, but if you can make it useful
that would be cool.
A while back Andrew Ho posted his script, apr, that is similar to
This behavior is documented in the guide...
http://perl.apache.org/docs/1.0/guide/config.html#Apache_Restarts_Twice_On_S
tart
- kyle
- Original Message -
From: Andreas Rieke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 18, 2002 1:41 AM
Subject: Double execution of
(at least those that you say matter) on every request. That's the
best you can do unless Perl starts supporting some method of side-by-side
versioning of modules.
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent
The warning applies to mod_perl 1.x. The reason is that mod_perl 1.0 is
single-threaded. In a UNIX environment, Apache (1.x) forks many child
processes to handle requests which each have their own embedded Perl
interpreter. In Win32, Apache has many threads to handle requests which all
share a
According to RFC 2396 (http://www.ietf.org/rfc/rfc2396.txt) the reserved
characters in the query component of a URI are ;, /, ?, :, @,,
=, +, ,, and $.
Apache::Util-escape_uri() does not escape :, @, , =, +, ,, or
$.
Something like the following should work:
use URI::Escape qw(uri_escape);
It looks like the default character class used by URI::Escape::uri_escape
changed in version 1.16 to be exactly the same as the one I suggested.
Older versions didn't escape the reserved characters.
- Kyle
- Original Message -
From: Kyle Oppenheim [EMAIL PROTECTED]
To: modperl List
Although I can't reproduce the behavior you describe (I get a message in my
error log plus the END block runs) I have seen something similar in the past
when $@ gets reset by an intervening eval block before Apache::Registry gets
a chance to log an error. In my case, I had a DESTROY handler on an
ap_make_etag returns. However, ETag's without vlv's are pretty much
backwards compatible.
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
) {
print $file-get ('data');
}
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
-Original Message-
From: Cristóvão Dalla Costa [mailto:cbraga;bsi.com.br]
Sent: Friday, October 25, 2002 4:31 PM
To: [EMAIL PROTECTED]
Subject: conditional get
Hi, I'm trying to get my
There are a few performance penalties when using Apache::Registry:
* Scripts are compiled at first request instead of server start
unless you
use something like Apache::RegistryLoader. So, the first
request per child
will be a little bit slower and you don't get to share memory
If you're writing new code then I would recommend writing handlers and
avoiding Apache::Registry altogether.
I had been thinking about whether to do this. Why do you
recommend avoiding
Apache::Registry? Is there a performance penalty for using it?
We sometimes use Apache::Registry
On Sat, 21 Sep 2002, Nigel Hamilton wrote:
to see the number of children and then make guestimates of
average per child memory consumption.
I'm not sure what the equivalent for other operating systems is, but
here's a Solaris tip for the archives... we use /usr/proc/bin/pmap to
. For scripts, this warning is usually harmless. You
can turn it off with the warnings pragma (Perl = 5.6.0):
no warnings qw(redefine);
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
-Original Message-
From: Boex,Matthew W. [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31
is
really fast compared to pthreads on your OS).
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
Are you setting the content-type header correctly? You can add the correct
content type a number of ways:
- Adding DefaultType text/html to your httpd.conf
- Using the AddType directive in httpd.conf to single out .pl files
- Add .pl files to your mime types config file (pointed to by
Amazon seems to include your session id in the URL in addition to a cookie.
I assume they do this to personalize when cookies are turned off and to
prevent proxy caches from caching personalized pages and serving them to the
wrong end-user. If you happen to type in a URL, they can revive your
That error is simply saying that your subroutines, my_start and p, aren't
defined in the current scope. The Apache::ROOT::vswap... is the package
name that Apache::Registry (or similar module, sounds like maybe EmbPerl in
your case) generated when it compiled your script.
Check to make sure
$r-no_cache(1) adds the headers Pragma: no-cache and Cache-control:
no-cache. So, you need to call no_cache before calling
$r-send_http_header. You can verify that it works by looking at the
headers returned by the server when you request your document. If your
browser is caching the page w/o
If you happen to type in a URL, they can revive your
session from the cookie. Pretty nifty trick.
This would seem to be a security hole to me. URLs appear in the logs
of the server as well as any proxy servers along the way. If the URL
contains reusuable auth info, anybody accessing
We've seen this happen before. Unfortunately, I don't have a fix for you
but I here's where we left off our chase...
1. ORA-03113: end-of-file on communication channel (for unknown reason,
maybe a network blip?)
2. We have some code that will catch this error and call DBI-connect again.
3.
slots and perhaps force httpd to
hit MaxClients if you segfault a lot.
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 8:33 PM
To: Kyle Oppenheim
Cc: mod_perl list
Subject: RE: Segfaults
Those warnings are normal, and you can use the warnings pragma to turn them
off. (Although, I believe the warnings pragma only exists in Perl 5.6.0+).
use warnings;
no warnings qw(redefine);
- Kyle
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf
Apache::Reload works by performing a stat on every file in %INC and calling
require for all the files that changed. It's quite possible that some of
the files in %INC are using relative paths (often '.' is in @INC). So, Perl
was able to load the file originally because the initial 'use' or
to
setting the no_cache flag in the request_rec. From the code in Apache.xs,
it seems like setting $r-no_cache(0) will unset the flag, but not remove
the headers.
--
Kyle Oppenheim
Tellme Networks, Inc.
http://www.tellme.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED
25 matches
Mail list logo
