Regarding 'make test' errors - Same here: Starting httpd... pid = 20592 ok
Testing mod_perl mode... #0 ascii... ok #1 pure.htm... ok #2 nooutput.htm... ERR:EOF instead of reponse status line Input: test/html/nooutput.htm Output: test/tmp/out.htm Log: test/tmp/test.log Testparameter: version = 2 repeat = 2 ERRORS detected! NOT all test have been passed successfully make: *** [test_dynamic] Error 1 > -----Original Message----- > From: Sean Conley [mailto:[EMAIL PROTECTED]] > Sent: Saturday, July 27, 2002 3:39 AM > To: Gerald Richter > Cc: [EMAIL PROTECTED] > Subject: Re: Cookieless Session Management > > > Here is what I have found... I went back and ran make test on > Embperl. > Most, but not all, of the mod_perl tests fail with the > message "ERR:EOF instead of reponse status line". For > example, test #131 completes fine. However when I run test > #130 it ends up with the following > message: > > Starting httpd... pid = 21027 ok > > Testing mod_perl mode... > > #130 mdatsess.htm... ERR:EOF instead of reponse status line > Input: test/html/mdatsess.htm > Output: test/tmp/out.htm > Log: test/tmp/test.log > Testparameter: > query_info = cnt=0 > cookie = expectno > offline = 0 > > ERRORS detected! NOT all test have been passed successfully > > It still remains that cookie based session management does > seem to work as it should, but cookieless sessions do not. > Whatever the case may be, they both behave differently to be > sure. I can watch session information being inserted into > the database whenever I am using cookie based session > management, and see by the logs that a session is maintained > since it gets the session_id and reports it. However, with > cookieless sessions this session id seems to be lost so a new > one is issued at the next request. Unless it is that the > session is expiring for some reason, and I am not sure how to > tell if this is the case. > And, for reference, I have Apache::Session v1.54 and > Apache::SessionX v2.00b3 installed. Both were installed by > using the CPAN shell, everything else I have downloaded and > installed from source myself. > > Enjoy the conference, and if you (Gerald) don't get a chance > to actually test this for awhile it is not going to be a big > problem. This is just a personal project otherwise I'd be > pushing for a commercial support license. However, I am one > of the many poor technical people that has been laid off, so > I don't have the money to buy a contract myself. :O) > > BTW, I do think Embperl is a VERY cool thing. I was > considering learning JSP, which still may happen just for > marketability, and found Embperl instead. I have been a Perl > nut for a few years now, and really am impressed with what > has become of Embperl. > > Any input from anybody on the above error would be > appreciated. As far as I can tell mod_perl is installed and > working properly. I installed it the same way I have a > hundred times before... but that doesn't mean I didn't have > it wrong all those times before as well. I can't run make > test on mod_perl since it is installed as a DSO, but if I > compile it into apache make test runs fine. I am baffled... > and it isn't the first time. > > Sean > > On Fri, 2002-07-26 at 16:13, Gerald Richter wrote: > > Sean and Justin, > > > > > > > > > I've done: > > > > > > EMBPERL_SESSION_MODE 2 > > > > > > Do I need to do something special other > > > than that? > > > > > > > Session management must be working at all. That means > Apache::Session > > and Apache::SessionX should be installed. If cookie based session > > management is working, then everything should be ok. To verfiy this > > further run > > > > make test > > > > and make sure that session mangement test are ok (and are > not skiped). > > > > If all this is given setting the session mode to 2 should be enough. > > > > Cookieless session management is a very new feature and not widely > > used,so maybe there is still a bug in Embperl, but I am > sure we will > > figure out what's going wrong. > > > > Gerald > > > > P.S. I am currently on the O'Reilly OpenSource Convention, > so I cannot > > test it right now. > > > > > > > > > > > > > -----Original Message----- > > > > From: Gerald Richter [mailto:[EMAIL PROTECTED]] > > > > Sent: Friday, July 26, 2002 5:24 PM > > > > To: Sean Conley; [EMAIL PROTECTED] > > > > Subject: Re: Cookieless Session Management > > > > > > > > > > > > Basicly you do the right thing and it should work. The > only thing > > > > I could see that is wrong is a missing > > > > > > > > Embperl_UseEnv on > > > > > > > > after the > > > > > > > > PerlModule Embperl > > > > > > > > without that Embperl will not look at the configuration > directives > > > > you set with PerlSetEnv. > > > > > > > > Gerald > > > > > > > > ----- Original Message ----- > > > > From: "Sean Conley" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Sent: Friday, July 26, 2002 9:41 PM > > > > Subject: Cookieless Session Management > > > > > > > > > > > > > I am using Embperl 2.0b8, and am having problems using > > > > > cookieless session management, achieved by setting PerlSetEnv > > > > > EMBPERL_SESSION_MODE 2. When this mode is set,the session ID > > > > > most definately is appended to the URL, however > modifying %udat > > > > no longer > > > > > has any effect. It seems that the session isn't > being tracked > > > > > properly. When using sessions with cookies > everything works as > > > > > expected including if I add an href to another page > the session > > > > > information in %udat is accessable in the second page. I > > > > did notice > > > > > in the debugging info that I get the message > > > > > [396]SES: Received Cookie ID: > 41ab2bf07a3eca989fa3548e1a89e37c > > > > > New Cookie ID: 41ab2bf07a3eca989fa3548e1a89e37c User data is > > > > modified when > > > > > the "default" mode is active. Whereas when > > > > EMBPERL_SESSION_MODE 2 is > > > > > set, the message is simply [396]SES: Received Cookie ID: > > > > New Cookie > > > > > ID: b8bf5c2763cf170360ec243d728ebcc9 User data is > NOT modified > > > > > for every request. > > > > > > > > > > Is there something that must be done differently when using > > > > cookieless > > > > > sessions? Are they not fully implemented yet? Is there > > > > documentation > > > > > somewhere that I am missing? Or is there something else > > > > entirely? I > > > > > have appended a copy of the pertinant configuration > > > > information at the > > > > > end of this email. As you can see, this is an EXTREMELY > > > > > simplistic test. I'm hoping that it isn't my own ignorance > > > > > causing > > > > the problems, > > > > > although that is the case more often than not. > > > > > > > > > > Thanks, > > > > > Sean > > > > > > > > > > httpd.conf: > > > > > > > > > > PerlSetEnv EMBPERL_COOKIE_PATH / > > > > > PerlSetEnv EMBPERL_COOKIE_EXPIRES +30m > > > > > PerlSetEnv EMBPERL_COOKIE_NAME testcookie > > > > > PerlSetEnv EMBPERL_SESSION_CLASSES "MySQL Semaphore" > PerlSetEnv > > > > > EMBPERL_SESSION_ARGS "DataSource=dbi:mysql:sessions > > > > UserName=username > > > > > Password=somepassword" PerlSetEnv EMBPERL_SESSION_MODE 2 > > > > > > > > > > PerlModule MD5 > > > > > PerlModule Embperl > > > > > > > > > > EMBPERL_LOG /usr/local/apache/logs/embperl.log > > > > > EMBPERL_OBJECT_BASE base.html > > > > > EMBPERL_DEBUG 2097168 > > > > > > > > > > Alias /embperl /usr/local/apache/embperl > > > > > > > > > > <Location /embperl> > > > > > EMBPERL_APPNAME test > > > > > PerlSetEnv EMBPERL_FILESMATCH "\.htm.?|\.epl$" > > > > > SetHandler perl-script > > > > > PerlHandler Embperl::Object > > > > > Options ExecCGI > > > > > </Location> > > > > > > > > > > test.html: > > > > > > > > > > [- > > > > > $r = shift; > > > > > if (!defined($udat{number})){ > > > > > $udat{number} = 0; > > > > > } > > > > > $udat{number}++; > > > > > -] > > > > > <html> > > > > > <body> > > > > > [+ $udat{number} +]<br> > > > > > </body> > > > > > </html> > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > --- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > --- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
