Hello Wendy, Is there anything we can do? I have worked with the MS DNA, .NET, SunOne, IBM Websphere frameworks and they all behave the same way by ordering the request parameters (first in first out). I know for sure that I am not the first one and neither the last one to have trouble with this kind of behavior using Tomcat. Even if the specification does not contain any direction on how to properly handle the request, Tomcat expected/ordered behavior would save hours of work to developers worldwide. I sure hope this issue is not an Open Source wake up call!
Thanks for all your help, Jeff -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, August 12, 2005 4:07 PM To: Tomcat Users List Subject: Re: Tomcat and the HttpServletRequest Object From: "Bhupinder Dhillon" <[EMAIL PROTECTED]> >I have the same bloody problem. The application is a generic form handler >that e-mails the form values. Most (all) of the clients expect the values >to be in the same order as the form itself. You are depending on arbitrary browser behavior. As far as I can tell, there's nothing preventing me from writing a browser that, say, alphabetizes the request parameters before sending them to the server. Yes, most browsers send them in the order they appear in the HTML source, but unless/until some statement about request parameter order makes it into the relevant specification, you depend on that behavior at your own risk. This isn't something that can be handled by the container-- even if Tomcat stops rearranging the request params, you have no control over the browser implementation. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
