----------------------------------------------------------------
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,
... We're just using simple (but nice) JServ, and our own servlet framework on top
(called 'versital' see http://www.tomoton.com) not Turbine...hey, it's a competing
product :)) Looks like its much the same thing... except for maybe the parameter
parsing
:)) But we'll soon get that straightened out... eh... won't we ? :))
Anyway... back to JServ... We shouldn't be parsing parameters ourselves... JServ should
do it (no ?) and get the session id out by itself (no ?)... If this is our bug, we're
perfectly willing to accept that, but let's first get this story straight... so don't
think Turbine... just good ole servlet API 2.0...
Sure your Turbine code works... are you saying you wrote your own parameter parsing on
top of JServ's ? We did that too for multipart... but does that mean you don't rely on
JServ's implementation of the 2.0 API anymore for the simple stuff ? It should get your
QUERY STRING parsed and stuff.... although with GET forms it doesn't really seem to
work
with us ...
e-gret,
Danny
[EMAIL PROTECTED] wrote:
> ----------------------------------------------------------------
> 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!!!
> ----------------------------------------------------------------
>
> > a. "If it is a POST request, then it is passed on the
> > input stream vs being passed within the QUERYSTRING"
> >
> > Yeah, we know GET should encode the parameters in the QUERY_STRING.
> > What I'm trying to tell you is that at the server side the QUERY_STRING does NO
> > LONGER - AND I REPEAT NO LONGER - contain the session parameter with GET
> > according to the servlet which processes the request, while the form action itself
> > DOES contain the session identifier in the QUERY_STRING. The host apparantly
> > never sees the session data. In the case of other parameters encoded in the
> > QUERY_STRING, they just disappear at the server side (or they were not properly
> > encoded in the QUERY_STRING in the first place).
>
> Then that is a bug in your code that pulls data out. Try creating a simple
> Servlet using my ParameterParser.java code. You will see that the
> variables do indeed make it into there. PP.java is in the
> org.apache.turbine.util package and is available from CVS in the Turbine
> package.
>
> > Now tell me, what the hell is going on ?
>
> Lets see your code that attempts to obtain this data. I put my code up and
> I know that it works. This is a bug in your code.
>
> > b. "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."
> >
> > One might expect someone like you to understand that the problem has been observed
> > in both cases you mention here. Why else would I bother to ask. Duh.
>
> Like I said, it works for me. Good luck with your code.
>
> -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]
--
--------------------------------------------------------------
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]
