I think that this case happens when you put HTML form on a static page,
OUTSIDE of Turbine. If you want to avoid this. Make welcome page INSIDE
Turbine (as Turbine template/screen/whatever), so when request comes to
your application, the session is already started, and you are safe from
Turbine url-encoded parameter passing. You can also try tweaking with
SessionValidator if you have very special needs. So the proposed code is
still valid, even in this case. The only thing I want to get rid of is
this useless stuff that compares "currentUri" and "duri" variables (at
least from my point of view) - not only it does it redundantly, it also
does it wrong (compare results for duri.toString() and
DymamicURI.toString(data) for "http://myserver/mycontext/myservlet/" and
"http://myserver/mycontext/myservlet" - watch out for last slash - try
for newly created window of your favorite browser - it reproduces
inifinite redirect quite reliably :).
Pals, think about dropping that stuff. If someone has anything against
it - please speak up ! We'll discuss it. I would like to see this stuff
removed, because "inifinite redirect" looks ugly on production sites
and, the way it's now implemented, it serves no purpose. Turbine works
just fine without it (I patched my private version of Turbine (latest
CVS) and it works equally well). I remeber some people discussed the
topic before. So probably there are still some issues about this stuff.
If there'll be no response, I'll assume everyone agrees, and I'll ask
Rafal to commit this stuff in.
Scooter
John Thorhauer wrote:
>
> Nissim wrote:
> > Sometimes, when you reload the homepage, the URL will be rewritten,
> > including the form parameters (username and password), because of the
> > code below. The parameterparser includes form elements, and the for
> > loop puts those into the pathinfo...so sometimes the password appears in
> > the URL. I don't really understand the purpose of that fragment, so I
> > can't make any suggestions, but I wanted to note that I have seen the
> > behaviour described above.
>
> I have had similar issues but havent had the time to look into it.
>
> John
> --
> ********************************
> ** John Thorhauer
> ** [EMAIL PROTECTED]
> ********************************
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
