Fix leading slash in path which creates a problem for S3 when URL path has double slashes #1494
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.
S3 throws an access denied when URL has doubleslashes in it, and having a leading slash in templates causes an access denied error. For example: https://mydjangosite.com//jquery/ajax.js would not work.
This fix removes a leading slash from the path and can be expanded to remove all double-slashes, however I feel that removing the leading slash is enough for most common scenarios.