use relative path for redirects avoiding problems with reverse proxies #486
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.
Since nginx doesn't rewrite
Location: ...
headers typing a padname like 'hello world' will result in a redirect to /p/hello_world instead of /pad/p/hello_worldYou can reproduce this bug on factor.cc/pad:
curl -v "https://factor.cc/pad/p/Hello%20World"
Redirecting to
./sanetized_pad_name
instead of/p/sanetized_pad_name
should fix this