In HTTP/1.1 a request (e.g., PUT) can have a body and the type of that body is identified by two headers: Content-Type and Content-Encoding. The Content-Encoding is typically used to compress the body and can be e.g., gzip or compress. A particularly large text file could be uploaded in compressed form with these headers: Content-Type: text/plain; charset=us-ascii Content-Encoding: gzip My question is, if a servlet receives such a request and calls getInputStream() what content would it see, the gzip'ed or ungzip'ed body? If the former then servlets allow a way for a server to be easily extended in the content-encodings it understands. If the later then the servlet engine must do the decoding and can easily identify encodings it doesn't understand and return a 415 HTTP error as it SHOULD do. If the former, then the servlet is responsible for doing this. Anyone know what's intended by the spec? Howard ___________________________________________________________________________ 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
