Sophana wrote:
> Christoph Zwerschke a écrit :
>> Maybe we should make '/' the default CookiePath again instead of None
>> (automatic determination)? This is less secure, but at least it will
>> always work (Microsoft policy ;-) This issue has already caused too much
>> confusion in the past.
>>
Christoph Zwerschke a écrit :
> Sophana wrote:
>
>> I reverted to 0.9.2 because of the cookie clear bug which I couldn't
>> find a workaround.
>>
>
> If you provide a test case for that bug, I'll try to fix it in the next
> version.
>
>
>>> But this would be redirected to /wk/wk/* and n
Sophana wrote:
> I reverted to 0.9.2 because of the cookie clear bug which I couldn't
> find a workaround.
If you provide a test case for that bug, I'll try to fix it in the next
version.
>> But this would be redirected to /wk/wk/* and not work anyway?
> No, in my case I only redirect / (^/$) wi
Christoph Zwerschke a écrit :
> Sorry for the late answer, I was offline was some weeks.
>
> sophana wrote:
>
>> Now looking at firefox cookie list, when I go to my server root url, I
>> get a SID cookie with the path set to //
>>
>
> This is a bug. It should only be '/'. I have already fix
Sorry for the late answer, I was offline was some weeks.
sophana wrote:
> Now looking at firefox cookie list, when I go to my server root url, I
> get a SID cookie with the path set to //
This is a bug. It should only be '/'. I have already fixed it in the
trunk. Can you try again with the HTTPR
Christoph Zwerschke a écrit :
> Concerning the sessions, this may have to do with the more secure
> default cookie path for Webware. It will be probably using '/wk' now,
> while you had been using '/'. If you still experience problems with the
> cookies, you can set a fixed cookie path in 0.9.4,
