-
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
Request without Host header fails with NullPointerException in ForwardedRequestCustomizer #5443
Labels
Bug
For general bugs on Jetty side
Comments
This kind of overlaps with #5437 ... |
joakime
added a commit
that referenced
this issue
Oct 13, 2020
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Opened PR #5445 |
joakime
added a commit
that referenced
this issue
Oct 13, 2020
+ Simplify isSecure handling in customize. + Simplify handling of `Proxy-Ssl-Id` header. + Simplify handling of `Proxy-auth-cert` header. Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Oct 13, 2020
+ Improve / document implied secure scheme behaviors for both `Proxy-Ssl-Id` or `Proxy-auth-cert` Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Oct 13, 2020
+ Additional tests for HTTP/1.0 + Overly complex negative test cases for `X-Forwarded-Proto: http` and `X-Proxied-Https: off` + Failure testcase for `X-Proxied-Https: foo` Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Oct 13, 2020
Additional NPE safety checks. Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Oct 13, 2020
The `X-Proxied-Https: off` case should have an implied port not a hardcoded port. Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Oct 13, 2020
Cleanup handling of forwarded.authority Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
PR #5445 merged (which fixes this) |
Impressive! 👍 |
joakime
changed the title
Request without Host header fails with NullPointerException in ForwardedRequestCustomizer with Jetty 9.4.32.v20200930
Request without Host header fails with NullPointerException in ForwardedRequestCustomizer
Oct 19, 2020
lucamilanesio
pushed a commit
to GerritCodeReview/gerrit
that referenced
this issue
Nov 30, 2020
This version, in particular, fixes the bug: "Request without Host header fails with NullPointerException in ForwardedRequestCustomizer" [1] This bug caused Gerrit to throw a NullPointerException when serving forwarded http/1.0 requests having no `Host` header set. [1] jetty/jetty.project#5443 Bug: Issue 13752 Change-Id: I9f9f7df74f6d6c3996e044ba9883b2aa8951c209
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
9.4.32.v20200930
Java version
11
OS type/version
Red Hat Enterprise Linux Server 7
Description
Requests (Healthcheck probes) using HTTP/1.0 without Host header started to fail after upgrade from 9.4.31.v20200723 to 9.4.32.v20200930 with http-forwarded module enabled.
Steps to reproduce:
Same test with 9.4.31.v20200723 does not fail.
NPE_ForwardedRequestCustomizer.txt
The text was updated successfully, but these errors were encountered: