* add a build.properties file containing git hash, build timestamp and scm url #1956
Signed-off-by: olivier lamy <olamy@webtide.com>
* move build infos to Jetty class so it's available for server and client
Signed-off-by: olivier lamy <olamy@webtide.com>
* apply changes by Greg review
Signed-off-by: olivier lamy <olamy@webtide.com>
Idle timeout have a special meaning in that they become a no-operation
if the application is dispatched but idle (neither reading nor writing).
HttpChannelOverHTTP2 now forwards the idle timeout to HttpInput, which
will only change its state if it is interested in reading.
HttpInput.consumeAll() has been modified to consume all input even if
it's already failed.
Failures caused by the other peer (e.g. I/O failures or stream resets)
are now retained and will eagerly consumed any queued data to free up
the flow control windows.
* Issue #1327 - Removing non-standard (Microsoft only) %uXXXX support
* Issue #1322 - Removing attempts at "solving" bad behavior in UrlEncoded
+ No longer captures NumberFormatException and Utf8Exception and
NotUtf8Exception for purposes of "recovering" from a bad encoding.
+ Introduces UrlEncode.decodeHexChar() and .decodeHexByte() to make
reporting of bad encoding more clear.
* Issue #1316 - throw a BadMessageException on bad parameter parsing
+ If BadMessageException is uncaught by the webapp, this will result
in an error 400 response message.
+ If an application decides to catch the BadMessageException, they can
choose to ignore the exception and do their own error reporting.
+ This piggybacks on Issue #1327 and Issue #1322
Tidy up write side.
It cannot be the same as the read side as there is no registration for write interest. There is only write operations and the
callbacks associated with them.
Fixed by calling tryFillInterested() rather than fillInterested() to
cope with the race between reads scheduling read interest and
setWriteListener() that also executes code in
HttpChannelState.unhandle() that wants to schedule read interest.
+ Reverting change to HttpTester.parseResponse(Input)
+ Providing new HttpTester.parsePartialResponse(Input)
+ InsufficientBytes tests no longer assert content strings with invalid
characters (this was breaks the surefire report xml)