https://bz.apache.org/bugzilla/show_bug.cgi?id=66499
--- Comment #6 from abernal <[email protected]> --- Checked against current trunk (f6b14daf42). The 302 loop described here no longer occurs. r1909769 (mod_http2 2.0.15) stopped converting a ":scheme" that differs from the connection scheme into an absolute URI. Only non-http(s) schemes get one now. Cleartext h2c with ":scheme: https" is served like any other request: GET /file.txt -> 200 GET /dir -> 301, same as with ":scheme: http" The Location of that redirect is "http://...";. This is not specific to HTTP/2: core builds redirects from the connection scheme (ap_http_scheme()), so a cleartext HTTP/1.1 request, even with an absolute "https://..."; request target, gets the same "http://"; Location. A backend behind a TLS terminator has to learn the original scheme from another source, as with HTTP/1.1. I did not check whether r1909769 has been backported to 2.4.x, so this may be fixed in trunk only. Unless someone knows of a remaining case, I think this can be resolved. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
