Stefane Fermigier (www.nuxeo.com) sent this answer this morning.
-- Message transmis --
Subject: [[EMAIL PROTECTED]: Apache Week issue 287]
Date: Sat, 16 Mar 2002 08:12:53 +0100
From: Stefane Fermigier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
- Forwarded message from Ap
Le Samedi 9 Mars 2002 23:04, Dieter Maurer a écrit :
> Jean-Paul Smets writes:
> > ... TCPWatch dumps demonstrating cookie problem for "__ac" cookie ...
>
> When I read the dumps correct then *ALL* Apache + "__ac" dumps
> lack the "__ac" cookie whether or nor VHM is used.
> Thus, I would say, VHM
Jean-Paul Smets writes:
> ... TCPWatch dumps demonstrating cookie problem for "__ac" cookie ...
When I read the dumps correct then *ALL* Apache + "__ac" dumps
lack the "__ac" cookie whether or nor VHM is used.
Thus, I would say, VHM is out of suspicion.
Now, Apache + Zope via "mod_proxy" is Zope
>
> You will see that the Set-Cookie is different in the 5 cases
>
> My conclusion for now is that something could be wrong with the Apache
> rewriting process.
Nope, cause I'm running Roxen.. and have the same behaviour.
/Magnus
___
Zope-Dev mail
Hi,
I did a few more tests. Apparently, this cookie issue
- happens in proxy mode
- does not happen in CGI mode
Of course, it is required to delete all cookies stored in the browser once
the __ac cookie has been successfully set in CGI mode
I have enclose an excerpt of my Apac
Le Mercredi 6 Mars 2002 22:35, Dieter Maurer a écrit :
> Jean-Paul Smets writes:
> > I could find out that certain cookie names work, some others do not
> >
> > Works
> >
> > Really strange.
>
> Could you use "tcpwatch" (or another TCP logger) to see whether
> the Zope response contains
On Thu, 7 Mar 2002, Magnus Heino wrote:
> > What browser are you using? Strange things like this happen for me
> > occasionally after a Mozilla upgrade, but I just delete the cookies for
> > the site and everything goes back to normal. I figure someone at
> > Netscape is just fiddling with the
> Jean-Paul Smets wrote:
> > I could find out that certain cookie names work, some others do not
> >
> > Works
> >
> > __ac_
> > __ac_ra
> > __ac_rak1
> > __ac_nex1
> > __ac_erp5
> >
> > Does not work
> >
> > __ac
> > __ac_rack1
> > __ac_rack12
> >
> > Really strange.
>
> What browser are you usi
Jean-Paul Smets writes:
> I could find out that certain cookie names work, some others do not
>
> Works
>
> Really strange.
Could you use "tcpwatch" (or another TCP logger) to see whether
the Zope response contains the cookie header. If not, this would
be a Zope problem we could debug.
Jean-Paul Smets wrote:
> I could find out that certain cookie names work, some others do not
>
> Works
>
> __ac_
> __ac_ra
> __ac_rak1
> __ac_nex1
> __ac_erp5
>
> Does not work
>
> __ac
> __ac_rack1
> __ac_rack12
>
> Really strange.
What browser are you using? Strange things like this happe
I can verify this. Same thing happens here too.
I had to redirect login_form to :8080 before, since I could not login to CMF
otherwise, using VHM.
I changed auth_cookie from __ac to __ac_, and now I can login through VHM...
Bug... I'll put it in the Collector.
(I'm using a week old cvs snapsh
I could find out that certain cookie names work, some others do not
Works
__ac_
__ac_ra
__ac_rak1
__ac_nex1
__ac_erp5
Does not work
__ac
__ac_rack1
__ac_rack12
Really strange.
JPS.
--
Jean-Paul Smets-Solanes <[EMAIL PROTECTED]> - Nexedi (CEO)
GPG Fingerprint: 40FF FA78 75AA 680D 8BB4 EEF9
I started debugging Zope. I found that the various methods in
CookieCrumbler are called and should normally set a cookie for auth_cookie.
However, under VHM operation, this does not happen when auth_cookie ==
'__ac'
I changed the name of the authentication cookie to __ac_erp5 in the CMF
(www.
Here are the news
- whener the CMF is access through a VHM, only one cookie is set
(__ac_name) and we get a loop on the login page
- whenever the CMF is accessed directly (in my case through an ssh tunnel
pointing to the root of the zope) two cookies are set (__ac=anA6YXRhbGFu%0
Le Mardi 5 Mars 2002 15:15, vous avez écrit :
> > I just upgraded this morning a Debian Woody server with Zope 2.5. The
> > upgrade has resulted in all my CMF (which use SiteRoot or
> > VirtualHostMonster) to refuse any authentication.
> >
> > Without SiteRoot or VirtualHostMonster, everything is
> I just upgraded this morning a Debian Woody server with Zope 2.5. The
> upgrade has resulted in all my CMF (which use SiteRoot or
> VirtualHostMonster) to refuse any authentication.
>
> Without SiteRoot or VirtualHostMonster, everything is fine.
I have had this problem (and a few others, some
Hi,
I just upgraded this morning a Debian Woody server with Zope 2.5. The
upgrade has resulted in all my CMF (which use SiteRoot or
VirtualHostMonster) to refuse any authentication.
Without SiteRoot or VirtualHostMonster, everything is fine.
I am searching the reason.
JPS.
_
17 matches
Mail list logo
