netty5

History

Nikolay Fedorovskikh dc98eae5a5 Correct filling an `origin` header for WS client Motivation: An `origin`/`sec-websocket-origin` header value in websocket client is filling incorrect in some cases: - Hostname is not converting to lower-case as prescribed by RFC 6354 (see [1]). - Selecting a `http` scheme when source URI has `wss`/`https` scheme and non-standard port. Modifications: - Convert uri-host to lower-case. - Use a `https` scheme if source URI scheme is `wss`/`https`, or if source scheme is null and port == 443. Result: Correct filling an `origin` header for WS client. [1] https://tools.ietf.org/html/rfc6454#section-4	2017-10-23 11:38:34 +02:00
..
src	Correct filling an `origin` header for WS client	2017-10-23 11:38:34 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2017-09-25 06:12:32 +02:00

Nikolay Fedorovskikh dc98eae5a5 Correct filling an origin header for WS client

Motivation:
An `origin`/`sec-websocket-origin` header value in websocket client is filling incorrect in some cases:
- Hostname is not converting to lower-case as prescribed by RFC 6354 (see [1]).
- Selecting a `http` scheme when source URI has `wss`/`https` scheme and non-standard port.

Modifications:
- Convert uri-host to lower-case.
- Use a `https` scheme if source URI scheme is `wss`/`https`, or if source scheme is null and port == 443.

Result:
Correct filling an `origin` header for WS client.

[1] https://tools.ietf.org/html/rfc6454#section-4

2017-10-23 11:38:34 +02:00

src Correct filling an origin header for WS client 2017-10-23 11:38:34 +02:00

pom.xml [maven-release-plugin] prepare for next development iteration 2017-09-25 06:12:32 +02:00