-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Migrating tomcat from jetty to jetty-9.4.29.v2020052 #5067
Comments
can you post your ngnix configuration? |
i already disable all the headers but still unable to figure it out which header is complaning about |
file one nginx:
file 2 nginx:
|
I can see few line starting with |
BTW if you really need those tab characters. |
but how can i change if i have jetty embedded inside the package:
i do not see or should i create new xml / modules there ? |
same RFC2616 twice ? |
Here i paste removing spaces and leave one space:
And the other file:
and some other file in case:
And some other one file:
|
typo to |
but read documentation as well |
not sure how you create your server but you can configure |
the issue was on this header: if i turn it off, then issue is gone. most likely that value is having some of those 3 characters
|
Jetty version
jetty-9.4.29.v2020052
Java version
openjdk version "11.0.5" 2019-10-15 LTS
OpenJDK Runtime Environment AppleJDK-11.0.5.10.1 (build 11.0.5+10-LTS)
OpenJDK 64-Bit Server VM AppleJDK-11.0.5.10.1 (build 11.0.5+10-LTS, mixed mode)
OS type/version
worun@rn-aosd-d00-lapp01:/Local/AS/Sentinel/packages/NemoDataSetsService-21-2-0-20200720-224046-4/lib$ uname -a
Linux rn-aosd-d00-lapp01.rno.apple.com 3.10.0-1127.8.2.el7.x86_64 #1 SMP Wed May 13 17:48:48 PDT 2020 x86_64 x86_64 x86_64 GNU/Linux
Description
After migrating from tomcat to jetty
Locally this endpoint looks to work fine, but with adding some headers from nginx is sending the following errors:
Bad Message 400
reason: Header Folding
Any idea how can one disable this particular issue or how to print which headers values are the one that causing the problem from nginx, is really hard to figure it out since nginx does not show any headers being passed, but locally works just that nginx sending specific headers that causes this issue
The text was updated successfully, but these errors were encountered: