Matt,

thanks a lot for your help for a second time.
These sess_ cookies come from PHP. Both PHP and mod_auth_cas have used
the same directory for saving cookies. Now I have moved the CAS cookies
to another directory and all errors are gone. Everything works perfectly.

Probably it is helpful to add this issue to any wiki/readme/... that the
CASCookiePath has to be a directory only for mod_auth_cas and not for
other software.


Bye,
Kevin



Am 02.06.2011 03:16, schrieb Smith, Matthew J.:
> Kevin -
> 
> Those "sess_"* cookies look really odd to me -- I don't think those could be 
> possibly be created by mod_auth_cas.  Is something else using that directory 
> for cookie storage?
> 
> HTH,
> -Matt
> 
> Matthew J. Smith
> University of Connecticut UITS
> [email protected]
> ________________________________________
> From: Kevin Richter [[email protected]]
> Sent: Wednesday, June 01, 2011 4:42 AM
> To: [email protected]
> Subject: Re: [cas-user] Bug with mod_auth_cas
> 
> I made a backup of the cookie directory.
> I opened the website and the "bad gateway" error occured.
> The logs said:
> 
> [Wed Jun 01 10:13:38 2011] [debug] mod_auth_cas.c(1501): [client
> 147.172.x.y] Cookie '6e6a87a99d0d1b34a770270240eada7b' is expired,
> deleting, referer: [...]
> [Wed Jun 01 10:13:38 2011] [debug] mod_auth_cas.c(946): [client
> 147.172.x.y] entering CASCleanCache(), referer: [...]
> [Wed Jun 01 10:13:38 2011] [debug] mod_auth_cas.c(988): [client
> 147.172.x.y] Beginning cache clean, referer: [...]
> [Wed Jun 01 10:13:38 2011] [debug] mod_auth_cas.c(1006): [client
> 147.172.x.y] Processing cache file 'sess_rj4fs2ebpai4vafd7h3eqmmuq6'
> [...]
> [Wed Jun 01 10:13:38 2011] [debug] mod_auth_cas.c(796): [client
> 147.172.x.y] Invalid cache cookie length for
> 'sess_rj4fs2ebpai4vafd7h3eqmmuq6', (expecting 32, got 31), [...]
> 
> Both files only exists in my backup cookie folder.
> 
> The contents of 6e6a87a99d0d1b34a770270240eada7b:
> <cacheEntry xmlns="http://uconn.edu/cas/mod_auth_cas";>
> <user>kevin</user>
> <issued>1306876655527835</issued>
> <lastactive>1306876656256984</lastactive>
> <path>/</path>
> <ticket>ST-92-eLtMDAidLnlY5st1djpc-cas</ticket>
> <secure />
> </cacheEntry>
> 
> The file sess_rj4fs2ebpai4vafd7h3eqmmuq6 is empty.
> 
> 
> Bye,
> Kevin
> 
> 
> Am 01.06.2011 09:38, schrieb Kevin Richter:
>> Hi,
>>
>> 1) Yes, always, with the same error. And after the gateway error the
>> first reload is always succeeding.
>> 2) Yes, always the same, "always expecting 32, got 31"
>> 3) Do you want the contents from the cookie?
>> If I count the tokens in the word "sess_bnofgn4qa9jhfrs7dvhgb4n6n2", it
>> *is* 31.
>>
>>
>> Bye,
>> Kevin
>>
>>
>>
>> Am 01.06.2011 03:12, schrieb Smith, Matthew J.:
>>> Kevin,
>>>
>>> I need a little more information:
>>> 1) Is this repeatable every time (with the refresh after the gateway error 
>>> always succeeding)?
>>> 2) Do you always see the "invalid cookie length" message, with the length 
>>> always being off by 1?
>>> 3) Can you send a copy of the cookie file with the invalid length?
>>>
>>> Thanks,
>>> -Matt
>>>
>>> Matthew J. Smith
>>> University of Connecticut UITS
>>> [email protected]
> 
> --
> You are currently subscribed to [email protected] as: 
> [email protected]
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-user
> 

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to