NOTE: If you are a developer, please use a private wiki based on foswiki/trunk on a daily base ...or use
trunk.foswiki.org to view this page for some minimal testing.
Use
Item9693 for docu changes for 1.2 and 2.0.
Item10412: Subtle problem with fragments in login form
| Priority: |
CurrentState: |
AppliesTo: |
Component: |
WaitingFor: |
| Urgent |
Closed |
Engine |
|
|
login.tmpl defines:
<form action='%SCRIPTURLPATH{"login"}%%PATH_INFO%' name='loginform' method='post' onsubmit='document.loginform.foswiki_origin.value+=window.location.hash'>
This appends the fragment from the url used to render the login form (not quite sure why, but presumably this is part of an attempt to maintain the fragment through a login sequence).
Unfortunately, if the foswiki_origin includes a parameter string, this ends up polluting the parameter string.
Given that the correct parameter values are expanded into hidden form fields anyway, the parameter string is redundant.
Copy-paste the following to a trunk/1.1.2 install to reproduce:
Starting from logged out state, click <a href="%SCRIPTURL{viewauth}%/%WEB%/%TOPIC%?blah=trueblah#target">here</a>
After you log in the value of blah will include the target
* blah: %URLPARAM{"blah"}%
--
CrawfordCurrie - 25 Feb 2011