Gerald Richter wrote:
The problem seems directly attributable to a 500
configuration error
occuring with a request that was using the session. These
configuration errors were occuring because of an error in our code
which was causing Storable to fail. It seems like the next
>
> > The problem seems directly attributable to a 500
> configuration error
> > occuring with a request that was using the session. These
> > configuration errors were occuring because of an error in our code
> > which was causing Storable to fail. It seems like the next
> connection
> >
> The problem seems directly attributable to a 500
> configuration error occuring with a request that was using
> the session. These configuration errors were occuring
> because of an error in our code which was causing Storable to
> fail. It seems like the next connection to a process that
Gerald Richter wrote:
Ok - I've done that. The SES: message always comes from the
parent process so it is not always easy to match the SESSION
data to the child process that is actually performing the request.
The question is, what are you seeing in case of the problem you have. Could
>
> Ok - I've done that. The SES: message always comes from the
> parent process so it is not always easy to match the SESSION
> data to the child process that is actually performing the request.
>
The question is, what are you seeing in case of the problem you have. Could
you quote the SES:
Ok - I've done that. The SES: message always comes from the parent
process so it is not always easy to match the SESSION data to the child
process that is actually performing the request.
I am wondering if my problems may be caused by using the stock threaded
perl even though we are using the old
nal Message-
> From: ___cliff rayman___ [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 14, 2005 6:56 AM
> To: [email protected]
> Subject: Session Problems Due to Apache Calling Back Into Itself
>
> It seems that when a REDIRECT is requested, apache/mod_perl
&
oops - editing below
___cliff rayman___ wrote:
It seems that when a REDIRECT is requested, apache/mod_perl chooses to
call back into itself, or resuse the same connection. In any case,
when certain redirects occur, the session is not written and the next
connection to use the process now has
It seems that when a REDIRECT is requested, apache/mod_perl chooses to
call back into itself, or resuse the same connection. In any case, when
certain redirects occur, the session is not written and the next
connection to use the process now has the same session id and session
data. It is not y
It seems that when a REDIRECT is requested, apache/mod_perl chooses to
call back into itself, or resuse the same connection. In any case, when
certain redirects occur, the session is not written and the next
connection to use the process now has the same session id and session
data. It is not y
Hi,
>
> I have a problem which may be related to sessions, I don't
> know if this has anything todo with SessionX / Embperl or
> what is causing this problem.
>
> The thing is we get alot of reports from a website that
> people suddenly get other peoples profiles etc. when they
> have loggon
: Tuesday, 28 September 2004 7:19 PM
To: [EMAIL PROTECTED]
Subject: Weird session problems
Hi!
I have a problem which may be related to sessions, I don't know if this
has anything todo with SessionX / Embperl or what is causing this problem.
The thing is we get alot of reports from a website
I'd check for use of globals to cache data - if a variable is not in the
default package, it's not cleaned at the end of the page. If I recall
correctly, we found another issue that caused data bleed in Embperl
1.3.3 - as memory serves, that version only cleaned scalars by default.
I've no idea if
a new user logs in?
Neal
From: Stefan Cars <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Weird session problems
Date: Tue, 28 Sep 2004 11:19:14 +0200
Hi!
I have a problem which may be related to sessions, I don't know if this has
anything todo with SessionX / Embperl or what is causi
Hi!
I have a problem which may be related to sessions, I don't know if this
has anything todo with SessionX / Embperl or what is causing this problem.
The thing is we get alot of reports from a website that people suddenly
get other peoples profiles etc. when they have loggon using their own
cr
>
> [32092]ERR: 24: Line 1: Error in Perl code: Permission denied at
/usr/lib/perl5/site_perl/5.6.0/Apache/Session/Lock/Semaphore.pm line 92.
> -
>
> I have read about the semaphores and that you can delete them (some of
them) and something about different users but this is above my know
Hi, I know this has been a topic that has been discussed in detail but I cannot find
my answer.
I am using Apache-Session 1.53.
If make test this archive I get this error message:
---
t/99mysqllock...(in cleanup) DBD::mysql::st execute failed: MySQL server has
gone away at blib/lib/Ap
d Williams
Cc: [EMAIL PROTECTED]
Subject: Re: Apache::Session problems after upgrading to Embperl 1.3.1
> No, I have mod_perl version 1.22.
> Adding PerlModule HTML::Embperl to my httpd.conf caused the server
> to die without complaint upon restart. There were no messages
> printed
> No, I have mod_perl version 1.22.
> Adding PerlModule HTML::Embperl to my httpd.conf caused the server
> to die without complaint upon restart. There were no messages
> printed to the screen or the logs.
>
> I am using Apache 1.3.9.
This should work normaly. Do you have compiled mod_perl as
nal Message-
From: Gerald Richter [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 26, 2001 11:29 PM
To: David Williams
Cc: [EMAIL PROTECTED]
Subject: Re: Apache::Session problems after upgrading to Embperl 1.3.1
>> PerlModule HTML::Embperl
>
> My server won't come up when I do th
>> PerlModule HTML::Embperl
>
> My server won't come up when I do this.
>
Looks like you have an old version of mod_perl and have build it as DSO.
This should work with any mod_perl version > 1.22 or if mod_perl is linked
staticly into Apache.
Gerald
P.S. Please reply also to the list
---
> I was running the correct version of everything all along, but
> what worked for me was changing the EMBPERL_SESSION_CLASSES
> variable from "PerlSetEnv EMBPERL_SESSION_CLASSES "DBIStore
> SysVSemaphoreLocker""
> to "PerlSetEnv EMBPERL_SESSION_CLASSES "File Semaphore"" in my httpd.conf
> file.
> No, I am using Apache::Session 1.53.
>
There is no file DBIStore which ships with Apache::Session 1.53. The
DBIStore is left over from Apache::Session 0.17. Change your configuration
to use a class under Session/Store and it should work.
Gerald
P.S. You could also specify the full package n
>
> Here's what's showing up in my Apache Error log now that I have
> upgraded from 1.2.1 to 1.3.1:
>
Looks like you are using Apache::Session 0.17. Embperl 1.3.1 doesn't support
0.17 anymore. Please upgrade to 1.53 and change you configuration
accordingly
Gerald
Gerald,
Here's what's showing up in my Apache Error log now that I have
upgraded from 1.2.1 to 1.3.1:
Cannot require Apache::Session::Store::DBIStore at
/usr/lib/perl5/site_perl/5.005/i386-linux/HTML/Embperl/Session.pm line 204.
I have all of the required files installed, however it seems like
> PerlSetEnv EMBPERL_SESION_CLASSES "FileStore NullLocker"
Must be EMBPERL_SESSION_CLASSES (missing S)
>
> First Step Now: I know I should be getting a msg at apache startup
> telling me that Session Management is enabled. I never do.
>
> - does this msg come from Embperl (and means that Embp
surprise!
I've found that my production server has Apache::Session running
allright, with almost the same config. Software versions are the same,
and httpd.conf says (comments relate to the differencies with the box
that doesn't work)
PerlModule Apache::Status
PerlModule CGI
hi,
there seems to be a lot of people here with problems with
Apache::Session and its integration with Embperl. I happen to be one of
them.
With the sincere hope that someone had solved this same problem
previously, I perused the list and found a few tips, but no solution.
Hi,
>
>
> $http_headers_out{'Location'} = "/login.html","main_content";
"main_content" has no effect. You cannot pass the target in a redirection.
> I get the impression that Embperl or Apache:Session sees the redirect/link
as a different browser?
Cookies are only send back by the browser to th
Hi,
I am using embperl 1.3.5b and Apache::Session 1.52
Before I could not get sessions to work at all but starting from this combination it worked fine, that is, until I stared using frames.
I have a frameset calling 2 normal html pages and 1 embperl page. (hello.html) The framename is main_co
Hi,
>
> I have some trouble getting session management to work. I'm using
> Apache Session 1.0, Embperl 1.3b3 with mod_perl 1.23 on Apache 1.3.12 on
> Win98.
>
> But when I tried to use SysVSemaphoreLocker I get a:
> Cannot require Apache::Session::SysVSemaphoreLocker at
> c./perl/site/5.6.0/lib/
Hi,
I have some trouble getting session management to work. I'm using
Apache Session 1.0, Embperl 1.3b3 with mod_perl 1.23 on Apache 1.3.12 on
Win98.
I have managed to start session-handling only when I am using
NullLocker.
I use the following entries in httpd.conf:
PerlSetEnv EMBPERL_DEBUG 1
P
32 matches
Mail list logo
