Heinz Wehner wrote:
> Chris,
>
> thanks for pointing me in the right direction. I've found the
> specs in API 2.2 section 5.1. The specs also list the condition
>
> "The content type is application/x-www-form-urlencoded"
>
> Our forms currently do not contain this MIME type spec.
> Can you elaborate a bit why this MIME type is required?
>
Browsers should default to this content type if you don't override it -- you
only need to set it explicitly if you are writing your own application, or
doing file uploads.
Generally, you always want to include a content type on any request or
response data sent over HTTP, so that the receiver knows what to do with it.
You can send anything you want -- file uploads (in a multipart format),
serialized streams of Java objects, XML-formatted, data, or anything else.
However, if you do one of these, the servlet engine needs to know that it
should not try to parse parameters from the input stream if you sent a POST
request.
>
> Regards,
>
> Heinz Wehner
> (Karlsruhe, Germany)
>
Craig McClanahan
___________________________________________________________________________
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
