Remy Maucherat wrote:
...2. blanks in multi-byte-range-requests After having added the header above, Acrobat sent byte-range-requests. But Acrobat choked. I did a packet filtering and recognized the following status code sent by Tomcat "416 request range not satisfiable". The reason was that Acrobat sent multi-byte-range-request using e.g. the following string "1000-2000, 3000-3010" Notice the blank character. It leads to a parsing exception in line 1300 of the DefaultServlet (Tomcat 4.1.30). If you do a trim() on the rangeDefinition obtained there, this error does not occur.
Please prove using the HTTP spec that it has to be done that way.
I think that's pretty clear from <http://greenbytes.de/tech/webdav/rfc2616.html#header.range> and <http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.2.1>.
...
Best regards, Julian
-- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
