-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
HTTP header key formatted problem #12395
Comments
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
i need help |
This having data, context, links and elaborate descriptions can help draw attention as there are hardly any resources here. You can even get more people to look at your messages on kubernetes.slack.com in the ingress-nginx-users channel (register at slack.k8s.io if needed) /remove-kind bug |
When I use curl https://example.com -H "CC: bb" |
That is expected behaviour. What is your expectation.
…On Sun, 24 Nov, 2024, 15:44 66li, ***@***.***> wrote:
When I use curl https://example.com -H "CC: bb"
I hope that the request header received by the backend service after
forwarding through nginx ingress is
cc: bb
In fact, nginx did not do any processing, and the HTTP header received by
the backend service is CC: bb
—
Reply to this email directly, view it on GitHub
<#12395 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWXQ7H36LKEYYTJ4JRL2CGRJLAVCNFSM6AAAAABSF3YQ5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHEYTSOJRHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I want to format the key in nginx ingress |
This background is my team's migration from Istio provided by cloud service providers to nginx |
Can nginx without Kubernetes do that ?
…On Sun, 24 Nov, 2024, 16:48 66li, ***@***.***> wrote:
I want to format the key in nginx ingress
curl https://example.com -H "CC: bb"
Backend service received
cc: bb
—
Reply to this email directly, view it on GitHub
<#12395 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWSWW5KEVEGKBURKART2CGYZDAVCNFSM6AAAAABSF3YQ5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHE2DOMRRHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It seems that, |
|
|
I think I'm not the only one who has encountered similar problems, |
Nginx does not have this feature as far as I know, unfortunately.
…On Sun, 24 Nov, 2024, 17:02 66li, ***@***.***> wrote:
I think I'm not the only one who has encountered similar problems,
The default configuration of Istio is to format all HTTP header keys
I don't know if there is an elegant solution on nginx ingress
—
Reply to this email directly, view it on GitHub
<#12395 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWUIYZEDXOY6WNBZW332CG2LTAVCNFSM6AAAAABSF3YQ5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHE2TENBVGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
ok |
We are not supporting custom scripts or server snippets etc in future
versions. So sorry for that. It's a good use in your case but it means
someone else make bad use of it.
…On Sun, 24 Nov, 2024, 17:13 66li, ***@***.***> wrote:
ok
Can I use Lua script to implement this feature? I am a newcomer to Lua, so
I need help
—
Reply to this email directly, view it on GitHub
<#12395 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWWGA3Q45JRKZEJCSCD2CG3XXAVCNFSM6AAAAABSF3YQ5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHE2TONBVGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
ok |
This is the first time I have seen this requirement. Why don't you join
slack at kubernetes.slack.com and ask. Register at slack.k8s.io .
…On Sun, 24 Nov, 2024, 17:18 66li, ***@***.***> wrote:
ok
Is there any other way to achieve similar functionality,
Lowercase all the keys in the HTTP header
—
Reply to this email directly, view it on GitHub
<#12395 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWUIL3GRFVOLRT2IJLD2CG4IDAVCNFSM6AAAAABSF3YQ5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVHE2TSNRRGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Expecting to convert all HTTP keys to lowercase, but in reality, this does not work,
Is there an existing solution for reference
The text was updated successfully, but these errors were encountered: