diff options
author | Maxim Dounin <mdounin@mdounin.ru> | 2020-12-10 20:09:30 +0300 |
---|---|---|
committer | Maxim Dounin <mdounin@mdounin.ru> | 2020-12-10 20:09:30 +0300 |
commit | ce9971b2b5c14982afede89635508334938ac520 (patch) | |
tree | 75d159374284c79ce9c1343f21279b0f701385f7 /src/core/ngx_array.h | |
parent | e62a5132ca6ab74f324bf46fe91ee89e1951578c (diff) | |
download | nginx-ce9971b2b5c14982afede89635508334938ac520.tar.gz nginx-ce9971b2b5c14982afede89635508334938ac520.zip |
Fixed parsing of absolute URIs with empty path (ticket #2079).
When the request line contains request-target in the absolute-URI form,
it can contain path-empty instead of a single slash (see RFC 7230, RFC 3986).
Previously, the ngx_http_parse_request_line() function only accepted empty
path when there was no query string.
With this change, non-empty query is also correctly handled. That is,
request line "GET http://example.com?foo HTTP/1.1" is accepted and results
in $uri "/" and $args "foo".
Note that $request_uri remains "?foo", similarly to how spaces in URIs
are handled. Providing "/?foo", similarly to how "/" is provided for
"GET http://example.com HTTP/1.1", requires allocation.
Diffstat (limited to 'src/core/ngx_array.h')
0 files changed, 0 insertions, 0 deletions