At 05:16 AM 5/17/2000 +0200, Gerald Richter wrote:
>Hi,
>
> > SetEnv EMBPERL_COOKIE_EXPIRES 10
>
>unfortunately Embperl cannot handle relativ expire times. It just passes the
>value you set in EMBPERL_COOKIE_EXPIRES in the http header to the browser,
>so it must be the full date. Remove the above line from your config and it
>should work. In this case the browser forgets the cookie when it is closed
>by the user.
I did this. Unfortunately, the problem is still occurring. I forgot to
mention something potentially of importance last time: the udat information
seems to propagate correctly when I submit a form; the problem arises when
I click a link. I did a packet capture of the transaction when I clicked
the link; the results are below.
The request:
GET /embperl/monitor/dosearch.shtml?start_item=10&num_items=10 HTTP/1.0
Accept: */*
Accept-Language: en-us
Host: 192.168.250.207
Via: 1.0 proxy3.trusecure.net:80 (Squid/2.0.RELEASE)
X-Forwarded-For: unknown
Cache-Control: max-age=259200
Connection: keep-alive
And the response:
HTTP/1.1 200 OK
Date: Wed, 17 May 2000 14:37:04 GMT
Server: Apache/1.3.12 (Unix) mod_perl/1.22
Content-Length: 8793
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/html;charset=iso-8859-1
Incidentally, even though I have set EMBPERL_DEBUG to 2369773, I never see
any information on cookies, even in cases where udat is clearly
working. Here's an illustration. Below, I do a packet capture for a
transaction where udat works. First I show the headers as revealed by the
packet capture, then I show the headers as indicated by Embperl's log file.
The request:
POST /embperl/monitor/dosearch.shtml HTTP/1.0
Accept: */*
Accept-Language: en-us
Content-Type: application/x-www-form-urlencoded
Host: 192.168.250.207
Content-Length: 164
Pragma: no-cache
Via: 1.0proxy3.trusecure.net:80 (Squid/2.0.RELEASE)
X-Forwarded-For: unknown
Cache-Control: max-age=259200
Connection: keep-alive
And the server's response:
HTTP/1.1 200 OK
Date: Wed, 17 May 2000 14:46:15 GMT
Server: Apache/1.3.12 (Unix) mod_perl/1.22
Content-Length: 82917
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Content-Type:text/html;charset=iso-8859-1
The Embperl log shows:
[508]HDR: 10
[508]HDR: Accept=*/*
[508]HDR: Accept-Language=en-us
[508]HDR: Cache-Control=max-age=259200
[508]HDR: Connection=keep-alive
[508]HDR: Content-Length=164
[508]HDR: Content-Type=application/x-www-form-urlencoded
[508]HDR: Host=192.168.250.207
[508]HDR: Pragma=no-cache
[508]HDR: Via=1.0 proxy3.trusecure.net:80 (Squid/2.0.RELEASE)
[508]HDR: X-Forwarded-For=unknown
At least this is consistent -- but where is the cookie that udat
uses?? And this is a case where the persistent information of udat
successfully propagated.
I admit I am completely lost at this point. I don't even know how Embperl
does what it does when it works, much less why it fails. Shouldn't the
browser be sending a Cookie: HTTP header in its request?
Any ideas or thoughts welcome.
steve
--
Steven D. Arnold Que quiero sera [EMAIL PROTECTED]
"We choose to go to the moon in this decade and do the other things, not
because they are easy, but because they are hard." -- John F. Kennedy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
