-
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
Add proxy-add-original-uri-header config flag #2353
Conversation
b0ff7a7
to
32f6a4c
Compare
This makes it configurable if a location adds an X-Original-Uri header to the backend request. Default is "true", the current behaviour.
Codecov Report
@@ Coverage Diff @@
## master #2353 +/- ##
==========================================
- Coverage 39.23% 39.11% -0.13%
==========================================
Files 73 73
Lines 5202 5203 +1
==========================================
- Hits 2041 2035 -6
- Misses 2872 2878 +6
- Partials 289 290 +1
Continue to review full report at Codecov.
|
/lgtm |
/approve |
@bashofmann thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aledbf, bashofmann The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This makes it configurable if a location adds an X-Original-Uri header to the backend request. Default is "true", the current behaviour.
Our use case, we have some internal services where the URL can be quite long, though still quite below nginx's large_client_header_buffers default limit. But by automatically adding the request URI as an additional header on the backend proxy request, a similar request header size limit from the backend web server, e.g. Jetty or another nginx, is exceeded.