unit.git/src/test, branch 1.11.0-2 Universal Web Application Server HTTP parser: fixed parsing of target after literal space character. 2019-09-17T15:40:21+00:00 Valentin Bartenev vbart@nginx.com 2019-09-17T15:40:21+00:00 6352c21a58d66db99f8f981c37e6d57e62fc24a2 In theory, all space characters in request target must be encoded; however, some clients may violate the specification. For the sake of interoperability, Unit supports unencoded space characters. Previously, if there was a space character before the extension or arguments parts, those parts weren't recognized. Also, quoted symbols and complex target weren't detected after a space character. 
In theory, all space characters in request target must be encoded; however,
some clients may violate the specification.  For the sake of interoperability,
Unit supports unencoded space characters.

Previously, if there was a space character before the extension or arguments
parts, those parts weren't recognized.  Also, quoted symbols and complex
target weren't detected after a space character.
HTTP parser: removed unused "plus_in_target" flag. 2019-09-16T17:17:42+00:00 Valentin Bartenev vbart@nginx.com 2019-09-16T17:17:42+00:00 3b77e402a903d9f7a6eeb32f7930d8979f8e0c9e 






HTTP parser: removed unused "exten_start" and "args_start" fields.
2019-09-16T17:17:42+00:00

Valentin Bartenev
vbart@nginx.com

2019-09-16T17:17:42+00:00

2fb7a1bfb90c4c8d484e4b0c4bd5ae2a594fd6e1












Introducing websocket support in router and libunit.
2019-08-20T13:31:53+00:00

Max Romanov
max.romanov@nginx.com

2019-08-20T13:31:53+00:00

e501c74ddceab86e48c031ca9b5e154f52dcdae0












Fixed lvlhsh test on 64-bit big-endian systems.
2018-11-15T10:00:58+00:00

Valentin Bartenev
vbart@nginx.com

2018-11-15T10:00:58+00:00

b033fb329fc14e6469596821508c487e3ed6ff82

The nxt_murmur_hash2() generated 4-byte hash that was stored in uintptr_t,
which was 8 bytes long on 64-bit systems.  At each iteration, it took the
previous key and hashed it again.

The problem was that it took only the first 4 bytes of the key, and these
4 bytes were always zero on 64-bit big-endian system.  That resulted in
equal keys at each iteration.

The bug was discovered on IBM/S390x.





The nxt_murmur_hash2() generated 4-byte hash that was stored in uintptr_t,
which was 8 bytes long on 64-bit systems.  At each iteration, it took the
previous key and hashed it again.

The problem was that it took only the first 4 bytes of the key, and these
4 bytes were always zero on 64-bit big-endian system.  That resulted in
equal keys at each iteration.

The bug was discovered on IBM/S390x.







Unit application library.
2018-08-06T14:27:33+00:00

Max Romanov
max.romanov@nginx.com

2018-08-06T14:27:33+00:00

1bb22d1e922c87d3c86c67bdce626767ee48fb5c

Library now used in all language modules.
Old 'nxt_app_*' code removed.

See src/test/nxt_unit_app_test.c for usage sample.





Library now used in all language modules.
Old 'nxt_app_*' code removed.

See src/test/nxt_unit_app_test.c for usage sample.







HTTP parser: relaxed checking of fields values.
2018-07-03T12:18:16+00:00

Valentin Bartenev
vbart@nginx.com

2018-07-03T12:18:16+00:00

11cecce11401a0c8990279406de3894c036c73a7

Allowing characters up to 0xFF doesn't conflict with RFC 7230.
Particularly, this make it possible to pass unencoded UTF-8 data
through HTTP headers, which can be useful.





Allowing characters up to 0xFF doesn't conflict with RFC 7230.
Particularly, this make it possible to pass unencoded UTF-8 data
through HTTP headers, which can be useful.







Introduced nxt_length() macro.
2018-06-25T13:51:47+00:00

Valentin Bartenev
vbart@nginx.com

2018-06-25T13:51:47+00:00

1a52d876f7e10d07f58deee6faeaf70a11a6110f












Style.
2018-04-05T12:49:41+00:00

Valentin Bartenev
vbart@nginx.com

2018-04-05T12:49:41+00:00

d15b4ca90639d0e6a5caab9ec905e49228072faf












Style: capitalized letters in hexadecimal literals.
2018-04-04T15:13:05+00:00

Valentin Bartenev
vbart@nginx.com

2018-04-04T15:13:05+00:00

0665896a5593fb41c92cbf164182a058ee40518c