Fix for rate limiting. nginx sublocations do not inherit all paramete… #708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A short explanation of the proposed change:
See pull request Introduce nginx configuration for rate limiting #657. @joachimjordan worked on this together with me and @petergtz. We noticed that when rate limiting is activated, this breaks the nginx config. Reason is that nginx does not document for each parameter if it is inherited by sub locations. The proxy_pass parameter is not inherited and thus must be duplicated for sublocations.
An explanation of the use cases your change solves
This fix adds the duplication for the proxy_pass parameter to the sublocations. Do you also require a test to ensure that this is working correctly? To test this, a CF installation is necessary with properties for the rate limiting added to the deployment manifest.
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
master
branchI have run all the unit tests using
bundle exec rake
I have run CF Acceptance Tests on bosh lite