summaryrefslogtreecommitdiff
path: root/modules/caddyhttp/headers/caddyfile.go
diff options
context:
space:
mode:
authorMatthew Holt <mholt@users.noreply.github.com>2020-05-20 11:33:17 -0600
committerMatthew Holt <mholt@users.noreply.github.com>2020-05-20 11:33:17 -0600
commit2a8a19856858dcaaf8d3233a2fc701e8a10c84a4 (patch)
treec62be62a6a441c88260994267b6cf6b2bc356ce5 /modules/caddyhttp/headers/caddyfile.go
parentcc8fb488d360f609d7e3aae773ec80c661505367 (diff)
reverseproxy: Don't overwrite existing X-Forwarded-Proto header
Correct behavior is not well defined because this is a non-standard header field. This could be a "hop-by-hop" field much like X-Forwarded-For is, but even our X-Forwarded-For implementation preserves prior entries. Or, it could be best to preserve the original value from the first hop, representing the protocol as facing the client. Let's try it the other way for a bit and see how it goes. See https://caddy.community/t/caddy2-w-wordpress-behind-nginx-reverse-proxy/8174/3?u=matt
Diffstat (limited to 'modules/caddyhttp/headers/caddyfile.go')
0 files changed, 0 insertions, 0 deletions