You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
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.
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
https://host.examplehttp://host.example/path.TODO:
unparsed_uriisn't as unparsed as its name implies?).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_uriis absolute.