The HTTP/1.1 Header Parser of the new HttpClient currently assumes that all
headers (names and value) are US-ASCII and as a result mis-decode any byte
whose value is > 127; For instance, 0x80 (128) gets decoded as a U+FF80 (65408)
instead of being either rejected or decoded as U+0080.
Historica
On 11/11/2020 10:14, Simone Bordet wrote:
Hi,
the javadocs for SocketOptions.SO_REUSEADDR states that: "This is used
only for MulticastSockets in java".
However, the javadocs for ServerSocket.setReuseAddress(boolean) goes a
great length explaining a behavior that applies to TCP sockets
(referen
Hi,
the javadocs for SocketOptions.SO_REUSEADDR states that: "This is used
only for MulticastSockets in java".
However, the javadocs for ServerSocket.setReuseAddress(boolean) goes a
great length explaining a behavior that applies to TCP sockets
(referencing SocketOptions.SO_REUSEADDR).
Similarly
