-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Milestone
Description
https://tools.ietf.org/html/rfc7230#section-5.3 suggests that clients can make requests of the form GET http://host.example/path HTTP/1.1, though in practice they don't for typical clients/servers.
It seems that this line:
nginx-sxg-module/ngx_http_sxg_filter_module.c
Lines 702 to 703 in 97ea78b
| snprintf(fallback_url, fallback_url_length, "%s%s%.*s", kHttpsPrefix, host, | |
| (int)req->unparsed_uri.len, req->unparsed_uri.data); |
https://host.examplehttp://host.example/path.
TODO:
- Verify this is a problem (maybe it's not because
unparsed_uriisn't as unparsed as its name implies?). - Fix it.
Given the rarity of this case, it seems low-priority, and I'd recommend the easiest solution, e.g. don't generate a SXG when unparsed_uri is absolute.
Metadata
Metadata
Assignees
Labels
No labels