----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
> Jon : It doesn't work here. I can reproduce it over and over again... Could
> you send an example of your working servlet ? I have read other people's
> remarks on this which seem to support the fact that any parameters included
> in the action attribute of a get-form, are overridden by the parameters from
> the form data. I couldn't get additional info on this in the HTTP rfc...
> anyone with extra info on how browsers do/are supposed to do this ?
Sigh, I already TOLD you where you can see my examples...look at the Jyve
FAQ. You have 100% source code as well as a perfectly running example.
You should *never* consider GET/POST as two different parameters. They are
the same thing and that is what the Turbine framework takes into
consideration with ParameterParser. The only difference is how the data is
passed to the browser. If it is a POST request, then it is passed on the
input stream vs being passed within the QUERYSTRING.
> I'm not sure whether this kind of evidence is conclusive, but the
> reconstruction of the request URL
> (request.getRequestURI()+"?"+request.getQueryString())) does not contain the
> session identifier. Does that mean that the browser didn't send it ? On the
> other hand, all the other logged requests are clearly showing the session
> identifier in the reconstruction, and yes, on the other side, the identifier
> is clearly displayed in the action attribute of the get-form under scrutiny
> (by inspecting the document source). Should we use a special encoding type ?
The session identifier is only shown if cookies in the browser are turned
off or you configure jserv to always pass it in the querystring.
> Anyway, as long as I can remember, for get-forms we always had to include
> the parameters as hidden inputs.. if there's a mistake made by us as far as
> using get-forms is concerned, I'd like to know about it, of course... the
> problem only became acute since support for URL rewriting suddenly became an
> issue.
Hidden parameters are not needed for GET or POST. In fact, this whole
issue has nothing to do with GET/POST, it has to do with passing
parameters within the QUERY_STRING, regardless of GET/POST.
Also, please do not forget to trim off the old message stuff...you only
need to quote the relevent portions of the emails.
-jon
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
