-----BEGIN PGP SIGNED MESSAGE-----
On the same note.... forwarding RIGHT after a forward does not work all too
redirects to 'self.forward(self.request().siteRoot()'
Which hits /Main.psp, Main.psp, using my security mixin, requires you to
login... and redirects you to 'self.forward(self.request().siteRoot()
Apparently the ../'s generated by self.forward() does not resolve until the
very end of the request... So you end up with:
So it looks like two things... the second redirect still thinks its in
/auth/action (even though it was called from /. And in addition to this...
the url still has the ../../ from the previous call in it. So when it tacks
its own ../../ to try and get to the root... well you get the picture.
Note that.. in Logout.py, if I use just go directly to /auth instead of /.. it
works as expected.
On Saturday 11 January 2003 11:03 pm, Luke Holden wrote:
> Hrm... I THOUGHT I sent an email to the list about this... but looking
> through my emails I dont actually see it... =)
> Anyways... Interesting problem...
> I have the following urls:
> When I try: 'self.forward(self.request().siteRoot() +"auth")' from
> Login.py... which generates: "../../auth"
> It seems to ignore the ../../ part... and I get the following error:
> The page you requested, /wk/auth/action/auth/, was not found on this
> However.... if I add a slash at the end.. :
> 'self.forward(self.request().siteRoot() +"auth/")'
> It works as expected.
> Maybe this was intentional? I don't know.. but its given me a LOT of grief
Main: (949) 387-5182
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----