Re: /login redirecting to /login_form

Carsten Agger <[email protected]> writes:
> According to this page:
>
> http://docs.plone.org/develop/plone/sessions/login.html
>
> you should be able to login and return to the original page by appending
> /login to the end of the URL.

This approach must have used some magic (likely the information about
the request referer) -- and as with all magic, there is the danger that
it does not work in some situations (for example, it is rumored that
in some situations, the request referer is not available).
Those cases can make the life difficult (as they happen only in special
situations, their analysis is difficult). And therefore, people may dislike
magic and prefer a reliable though less comfortable behavior.
This might be the reason for the change you observe.

Espen already mentioned one approach to make "referer" based login
redirection again available in your system.

However, the more comfortable approach likely is to forget
"appending '/login' to the url" completely and instead use an (intelligent)
action to log in. Rather than manually editing the browser's
address input field, the user sees on its page an interaction element
(link or button) "login" and when it presses this element, he is
redirected to "login_form" with the "came_from" parameter containing
the original url. It is this way Plone tries to support login.


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk