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

Kong dropping some of the request headers #3586

Closed
tejas3190 opened this issue Jul 3, 2018 · 4 comments
Closed

Kong dropping some of the request headers #3586

tejas3190 opened this issue Jul 3, 2018 · 4 comments

Comments

@tejas3190
Copy link

As observed from Wireshark, Kong is not forwarding all the headers to upstream.
I am trying to send a request with following headers.

  1. "com.bea.wlcp.wlng.plugin.sms.RequestDeliveryReportFlag":"true"
  2. "test": "ok"

At the upstream server "com.bea.wlcp.wlng.plugin.sms.RequestDeliveryReportFlag":"true" is not coming. Does kong has any limitation ?

  • Kong version (0.13.1)
@bungle
Copy link
Member

bungle commented Jul 3, 2018

I suppose you also get something like this in error.log:

2018/07/03 17:12:42 [info] 3562#796588: *782 client sent invalid header line: "com.bea.wlcp.wlng.plugin.sms.RequestDeliveryReportFlag: true" while reading client request headers, client: 127.0.0.1, server: kong, request: "GET / HTTP/1.1", host: "kong.test:8000"

@bungle
Copy link
Member

bungle commented Jul 3, 2018

Kong by default uses a lot of Nginx defaults. If you need to change this, you need to have this:
http://nginx.org/en/docs/http/ngx_http_core_module.html#ignore_invalid_headers

set to:

ignore_invalid_headers off;

As this is Nginx configuration setting, and we are using the default, I feel this is more like a configuration issue on your side, so I will close this.

@bungle bungle closed this as completed Jul 3, 2018
@bungle
Copy link
Member

bungle commented Jul 3, 2018

This will come with 0.14.0:
#3530

So you don't even need to use custom nginx configuration there anymore to change this.

@tejas3190
Copy link
Author

Thanks you are right

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants