Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traefik camel cases response headers #1969

Closed
davidgenn opened this issue Aug 18, 2017 · 1 comment
Closed

Traefik camel cases response headers #1969

davidgenn opened this issue Aug 18, 2017 · 1 comment

Comments

@davidgenn
Copy link

davidgenn commented Aug 18, 2017

Do you want to request a feature or report a bug?

Bug

What did you do?

Traefik in consul-catalogue mode.

What did you expect to see?

Traefik returns backend response headers un-altered.

What did you see instead?

Headers are camel cased eg:

X-MY-APPLICATION-HEADER: 12345

is returned as:

X-My-Application-Header: 12345

Output of traefik version: (What version of Traefik are you using?)

1.3.5

TOML

[consulCatalog]

endpoint = "127.0.0.1:8500"
domain = "service.consul"

frontEndRule = "Host:{{ServiceName}}.{{Domain}},PathPrefixStrip:/{{ServiceName}}"
prefix = "traefik"
@ldez ldez added the kind/question a question label Aug 18, 2017
@ldez
Copy link
Member

ldez commented Aug 18, 2017

RFC 7230 (and also 7540) states:

"Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace."

Golang http server rewrites all headers in a canonical way and your backends shouldn't rely on case sensitivity golang/go#5022.

Duplicate of #1756 #466

@ldez ldez closed this as completed Aug 18, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants