Hi,
Excuse me for this question that is, without question, due to my newbie-
ness, but I am against a wall here. I am creating a website that is running
under mod_perl and using several handlers of the chain. The website uses
the POST method to send form data.
I first used Apache::Request-new()
This is the only error line that appears in the error_log.
[Sun Mar 2 20:10:19 2003] [notice] caught SIGTERM, shutting down
Perhaps it's me, but could you please create a copy-n-paste mail
with the (correct) relevant code snippets (httpd.conf, startup.pl,
etc.). This might help.
Best
Hi,
I am workin on a site where all pages are handled via an Apache::SSI
descendant. Some included parts are itself mod_perl routines that
use the instance-methode to recreate the request. The routines work
fine if used standalone but as soon as the routine gets included
via the SSI method
this has been asked before, and I've found in the archives
there is no way I could have a logout page for the Basic Auth in
apache.
Is there nothing I can do ? This is required only for the
development team, so we need to let mozilla or IE forget
about the username and password.
And
Regarding my previous post:
... The routines work
fine if used standalone but as soon as the routine gets included
via the SSI method (subrequest?) apache/mod_perl complains. The call
to instance results in an error 'can't locate method 'pnotes' via
package X::Y::Z', where X::Y::Z my own
Hi,
Well, by now you must know that I am working on something... and I
keep stumbling on things I seem not to understand and not to be
able to find in the docs / books.
See this example:
Location /
# SetHandler perl-script
PerlHeaderparserHandler MyClass-first
PerlAuthenHandler MyAuthen
Comparing your post and that of others, I see that you use
Authentication through mod_perl. What happens if you completely
disable Authentification? Do you still experience the same
problem?
--Frank
Hi Todd,
Trying to logoff using Basic Auth is becoming something of a faq...
if there was a means by which i could strip out the Authorization
header in the client request, this would force a 401 response from
the server which would also satisfy my specific need.
I doubt if this will work. I
On Fri, Apr 04, 2003 at 03:34:25PM +0200, Frank Maas wrote:
You can set a session (see Apache::Session and related modules) that
can use the uri as session-container as well (eg
http://www.example.com/9o79876a98d7fa98d7/path/to/doc). The session
part (9o79876a98d7fa98d7) can be stored
On Fri, Apr 04, 2003 at 10:13:59PM +0200, Frank Maas wrote:
On the latter I totally agree. To avoid the session snatching you
describe, you can store IP addresses on your site in the database.
You won't solve proxyserver-problems with this though. So what about
the following approach
I'm trying to write a authentication handler using mod_perl, and am
encountering some difficulty. I have isolated my problem to the usage
of the lookup_uri($uri) function call - whenever I call it, my module
segfaults. I have tested the input with both a variable string, and
just a quoted
well, the (long) wait is now over - Practical mod_perl is here.
Geoff, you might be the best person to ask and it might be a worthwhile
extension to the mod_perl-documentation: why would one use this new
book if (s)he has the mod_perl cookbook already. I am not trying to
set a new war between
Perrin Harkins wrote (in a discussion with Michael L. Artz):
Well, I figured that the AuthenHandler already parsed the
authentication cookie and declared it valid, so I didn't really see
a point the in doing it at the beginning of every script. $r-user
just seemed more intuitive to me.
Are you using 'lookup_uri' or another form of subrequest somewhere
in your handlers? Try tracing your request and see where it goes
wrong. I had similar problems and it pointed out to be an error in
a subrequest. Consult the mailinglist archive if you want.
--Frank
I have handler that looks
Hi,
Recently I found some strange behaviour of the caching-functionality of
Apache. I had configured one httpd as caching proxy and a second one
creating the pages. Two kind of pages are created: dynamic ones (with
no_cache(1)) and static ones (with an expiry set to some minutes or
hours).
What I
On Fri, 2003-07-25 at 04:32, Frank Maas wrote:
Come to think of it, I have never had problems with mod_proxy caching
thing I didn't want cached. Quite the opposite -- I had to be very
careful with Expires headers to get anything cached at all.
I think you might be mis-diagnosing
http://server.domain.com/cgi-bin/MyProcedure.pl?cust_id=x
I'd like to make a cron job to source the above PERL script as from
the command line to resemble something like:
perl /usr/local/apache/cgi-bin/MyProcedure.plneed to pass the
parameter here as cust_id=x
I am very doubtful
On Tue, Aug 12, 2003 at 11:50:01AM +0200, Dirk Lutzebaeck wrote:
Dennis Stout writes:
On a whim, I would try writing a second script to do the actual shutdown and
restart of Apache.
Then have your mod_perl program either run it in the background (with a ) or
fork it into another
I'm wondering why it is impossible?
I am not exactly sure here, but I think this is because a TransHandler
is definitely not allowed inside a Directory or File container. And
since Apache does not make the distinction between containers (it uses
the constant RSRC_CONF to disallow a directive
On Thu, Aug 14, 2003 at 11:07:13AM -0400, Geoffrey Young wrote:
There is actually a Location/LocationMatch sequence performed just
before the name translation phase (where Aliases and DocumentRoots are
used to map URLs to filenames). The results of this sequence are completely
thrown
and want to unset the TransHandler inside the Location.
How to do that?
AFAIK: not. The TransHandler is the first to be called and cannot appear
inside a container (ref. ModPerl cookbook). The only thing I can think of,
and in fact implemented this, to make the TransHandler URI-aware and
B. Fongo wrote:
Script_name.pl: Use of uninitialized value in concatenation (.) or
string at output_tab.pm line 42.
Perrin replied:
This is a standard perl error message. It is not related to mod_perl.
You can look in the perldiag man page for a more complete explanation.
B. Fongo wrote:
On Sat, Aug 23, 2003 at 01:55:03PM +0200, Marcel Greter wrote:
This is not a very good solution. You would also catch the case where $_
is 0, which may should not happen. You would better do
Yes... I always fall into that pithole. I think this is because I find
the 'defined(...) ? ... : ...'
I'm afraid that is not a very good article. It's out of date,
...
Apache::Session::DBI (which is what the article refers to) is ancient
and should not be used.
I stumbled upon this problem quite a few times. Trying to get the hang
of using cookies for authentication and sessions there are
Stas Bekman wrote:
Perrin Harkins wrote:
Zack Brown wrote:
I'd like to implement something that tries to ensure that one user
can't masquerade as multiple users.
We talked quite a bit about preventing multiple logins recently. I
think it was last week. Check the archives.
Ged wrote:
How to avoid multiple logins?
The short answer is: you can't.
Sure you can. Charge $10 per login.
I don't want to clobber the list with non-technical trivia, but
even when you charge money, you can't avoid it. If only there is
one user that is willing to pay the amount twice,
26 matches
Mail list logo
