[Zope] Re: cookie crumbler - preserving variables in URL

[Tino Wildenhain]

Hi,

Am Do, den 19.08.2004 schrieb Maciek Pasternacki um 19:01:
> On Boomtime, Bureaucracy 13, 3170 YOLD, David Siedband wrote:
> 
> > Often, the pages that require authentication have a variables on the
> > end of the URL.
> >
> > http://www.site.org/updateListing_html?pid=22
> >
> > After authentication, these variables get dropped generating an error
> > for the dropped variable
> >
> > redirects to:
> >
> > http://www.site.org/updateListing_html
> 
> I have similar problem with traverse_subpath; I have ZPT, say
> http://server/Template, which I call as
> http://server/Template/Something and I read traverse_subpath in the
> template to render wanted output; when Unauthorized is raised,
> CookieCrumbler redirects to http://server/Template.  It seems to use
> <offending_object>.absolute_url() instead of REQUEST.URL to redirect.
> 
> I think I'll try to use Python script, which will call the ZPT, catch
> Unauthorized and redirect manually to
> /login/login_form?came_from=<correct_address>.  It's surely a kludge, but
> easier to write and maintain through upgrades than patching
> CookieCrumbler.

Well. Whats wrong with just leaving the request/URL allone,
and dont do any redirect but just check for authentication
bring up the auth page in place?

I never get it why almost all userfolders do redirects.

Regards
Tino