Hi,
Java/Servlet/jsp world there are two types of http forwards/redirect
redirect - This is make a complete new request, loose all the request
parameters
forward- Will preserve all the information (e.g parameters) and forward to
the other URL
in mod_perl when we make a redirect (using the
Tracy12 wrote:
Hi,
Java/Servlet/jsp world there are two types of http forwards/redirect
redirect - This is make a complete new request, loose all the request
parameters
forward- Will preserve all the information (e.g parameters) and forward to
the other URL
in mod_perl when we make
doesn't exist. Is the correct way to return a 301 to use
Apache2::Const::HTTP_MOVED_PERMANENTLY ? I keep thinking that i've read
somewhere that using the ::HTTP* constants isn't a good idea.
Adam
Will Fould wrote:
I have a strange issue with a particular script that sometimes (often)
generates a 302 to another script without a clear reason why.
Oddly enough, I simply placed a few warn('blah') code snippets to
crudely determine from the error log where it was happening in
production
On Tue, 2007-01-16 at 16:45 -0800, Will Fould wrote:
I have a strange issue with a particular script that sometimes (often)
generates a 302 to another script without a clear reason why.
Are you saying that you don't have any code in the script that generates
redirects, but they sometimes happen
On Wed, 2007-01-17 at 10:25 -0500, Adam Prime x443 wrote:
doesn't exist. Is the correct way to return a 301 to use
Apache2::Const::HTTP_MOVED_PERMANENTLY ? I keep thinking that i've read
somewhere that using the ::HTTP* constants isn't a good idea.
This thread covered it pretty well:
Is it possible to get the file descriptor for the client socket from the
RequestRec?
I.e. something like $r-FILENO (which doesn't seem to work) or perhaps
$r-connection-client_socket-os_sock
(os_sock exists in the APR structure in C, but there doesn't seem to be a perl
accessor method.)
Hi,
My perl authentication handler works fine BUT the biggest problem inside my
Auth handler I do some resource intenstive tasks and if everything
successful set the REMOTE_USER env variable.
But for the subsequent requests from the same user (after the initial
Authentication is successful) how
Daniel Risacher wrote:
Is it possible to get the file descriptor for the client socket from the
RequestRec?
I.e. something like $r-FILENO (which doesn't seem to work) or perhaps
$r-connection-client_socket-os_sock
(os_sock exists in the APR structure in C, but there doesn't seem to be a perl
Tracy12 wrote:
My perl authentication handler works fine BUT the biggest problem inside my
Auth handler I do some resource intenstive tasks and if everything
successful set the REMOTE_USER env variable.
But for the subsequent requests from the same user (after the initial
Authentication is
What about the security measures if we store authenticated user information
in a cookie,
Cant we handle in the server session and and store it as a session variable.
This would be much secure?
Robert Landrum wrote:
Tracy12 wrote:
My perl authentication handler works fine BUT the biggest
Assuming your not re-using session variables, you might want to verify that
your package names do not conflict and that your conditions for any redirects
are not confused. I remember fighting this in a previous life.
B
On Wednesday 17 January 2007 08:24, Perrin Harkins wrote:
On Tue,
Well does this all mean there is limited features to do session handling on
mod_perl. Well I am new to mod_perl but in JAVA/Servlet you can do a simple
thing like this
request.getSession().setAttribute(my_remote_user,uid of the authenticated
user);
for subsequent requests we can retrieve this
On Wed, 2007-01-17 at 14:50 -0800, Tracy12 wrote:
What about the security measures if we store authenticated user information
in a cookie,
Cant we handle in the server session and and store it as a session variable.
This would be much secure?
Have you looked at the Apache::AuthCAS module on
On Wed, 2007-01-17 at 16:11 -0800, Tracy12 wrote:
Well does this all mean there is limited features to do session handling on
mod_perl.
Concepts like sessions are not built into mod_perl. They are
implemented separately by modules that you can find on CPAN, like
Apache::Session, which was
Apache::AuthCAS module on CPAN does not support OPEN SSL also it creates
database tables to store data, we tried it on Apache 2.2 with mod_perl 2.0
it failed. We need only a serviceValidate from CAS not other functions.
mod_cas looks ok but does not supports Apache 2.2
We have almost finish
On Jan 17, 2007, at 7:11 PM, Tracy12 wrote:
Well does this all mean there is limited features to do session
handling on
mod_perl. Well I am new to mod_perl but in JAVA/Servlet you can do
a simple
thing like this
request.getSession().setAttribute(my_remote_user,uid of the
authenticated
CGI::Session looks like it gives a good abstraction.
I used use CGI::Session; in my code and came up with the error failed to
resolve handler `AuthCAS-authen_handler': Can't locate CGI/Session.pm in @
I am using fedora core 5 with Apache 2.2 with mod_perl 2.x
Can I know how can I install the
Tracy12 wrote:
Can I know how can I install the above module(CGI::Session) to my system.
There is lots of good documentation about installing perl modules. You
can read the perlmodinstall man page. You can pick up a good book like
Intermediate Perl. There is a discussion about CPAN
-8-- Start Bug Report 8--
1. Problem Description:
Two failures in make test building mod_perl 2.0.3
2. Used Components and their Configuration:
*** mod_perl version 2.03
*** using /tmp/mod_perl-2.0.3/lib/Apache2/BuildConfig.pm
*** Makefile.PL
20 matches
Mail list logo
