Roland Weber wrote: > I'll change the parsers, including the constructor of BufferedHeader, > to throw a ProtocolException instead. That will also show up in > Header.getElements(), which probably affects the cookie code.
I had to give up on that idea. Cookie and Auth create BufferedHeader from data they generated. It would have been a lot of effort to no avail. I've defined an unchecked ParseException instead, so that it is no longer necessary to map InvalidArgumentException to ProtocolException when the check in BufferedHeader.<cons> is actually relevant. The parser code for header values doesn't check for parse errors anyway. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
