>>> Garth Somerville <[EMAIL PROTECTED]> 15-May-00 9:27:49 PM >>> >Now I'm getting confused ;-) >Either his servlet reads the form data or the container does it >-- they cannot both do it. I think I was alseep - sorry for confusing you. I was suggesting that if the container asks the parameter table for the session id then it might work after the parameter data had been scanned. But of course it won't, for 2 reasons: 1. the session is encoded in the query string not the POSTed data 2. the servlet container does not have access to parameters passed outside of the engine. In fact the reverse to what I suggested might be true: - the engine has a better hope of reading the session correctly before the data has been parsed because then it is limited to just the query string Mind you - the container shouldn't be looking for the session id in the POST data anyway because it can never be there. The problem the guy is having is bizarre and apparently Allaire have it down as a recognised problem - I can't see how it can be a problem though since looking for the session id in the query string should be a simple matter of doing just that and ought not to be complicated by what is in the request body at all. *Possible solution* I can think of one further way you could hack round the problem - find out what the Allaire session manager is called and how to call it to create a session - introspection should be able to tell you that. Once you've done that you can use the id directly to obtain a session. Makes the code unportable but does fix the problem. Nic Ferrier ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
