[Twisted-web] Strange Guard Behaviour
federicotom at yahoo.it
Fri May 8 20:49:13 EDT 2009
I have a particular (a little bit difficult) scenario and
something is not working as I think, can't understand why.
I'm launching, in the same process, two guard`ed application:
A ~> localhost:8080
B ~> localhots:9090
Running Apache and depending by the requested segments, I
proxy the request to A or B (fqdn is always the same and
if segs == 'foo':
If I do:
1) I login A (not anonymously). All works.
2) With the same Browser, I login to B (not anon).
All is working.
Now, making the following requests, something strange happens:
the B resource is (correctly) returned.
Apache is proxing the request to B.
the request is (correctly) forwarded to A... but
the B resource is returned!
* https://fqdn/some/url/here/ (some <> foo)
the A resource is returned, Apache proxing
(correctly) to A.
I'm really blue, because I can't understand the
different behaviour between "/" and "/notfoo/".
Apache proxies to A, but in the first case B
is returned, in the second, A is returned.
- cookieKey is different for the two resources
- I'm sure, reading apache logs, that requests
are correctly proxied.
Do you have some idea?
Today is Pungenday, the 55th day of Discord in the YOLD 3175
More information about the Twisted-web