On Tue, Jun 04, 2002 at 12:47:07AM -0500, Ian Bicking wrote: > However, this doesn't solve your problem as you were talking about > non-urlencoded input with no content-type to indicate that... if at all > possible, I'd change these clients. text/xml will work (though be > inaccurate), while text/plain seems more appropriate. To capture the > input with no content-type, there'd have to be some setting to copy the > input before it was sent to FieldStorage (it probably shouldn't do this > by default, as it would consume more memory and web services *should* > pass proper content-types, though that won't help you yet).
Having a setting sounds like a good route. If it's off, it won't cause any overhead. If it's on, it will allow the maximum flexibility both for servlets using POST variables and for servlets using stdin for some other purpose, even if both servlets exist in the same application, and even if some browsers forget to set the Content-type. We'd just have to make sure FieldStorage doesn't blow up if given random input. -- -Mike (Iron) Orr, [EMAIL PROTECTED] (if mail problems: [EMAIL PROTECTED]) http://iron.cx/ English * Esperanto * Russkiy * Deutsch * Espan~ol _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
