|
From: | martin.winter at siemens dot com |
Subject: | [Bug classpath/46063] New: User-defined Content-Encoding throws exception |
Date: | Mon, 18 Oct 2010 06:34:19 +0000 |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46063 Summary: User-defined Content-Encoding throws exception Product: classpath Version: 0.98 Status: UNCONFIRMED Severity: normal Priority: P3 Component: classpath AssignedTo: address@hidden ReportedBy: address@hidden I'm working with HttpUrlConnection exchanging data with a user-defined Content-Encoding. The processing in gnu.java.net.protocol.http.Request:503 however throws a ProtocolException on all unknown Content-Encodings. The behaviour of the Sun JRE however (and also what I would expect) is to let the application handle an unknown content encoding. My proposal: Replace 505: throw new ProtocolException("Unsupported Content-Encoding: " + 506: contentCoding); by 505: return in; At least encodings starting with "x-" should be allowed to be handled by the application.
[Prev in Thread] | Current Thread | [Next in Thread] |