Take FORCE_SCRIPT_NAME setting into account#38
Merged
noirbizarre merged 6 commits intonoirbizarre:masterfrom Jun 27, 2014
Merged
Take FORCE_SCRIPT_NAME setting into account#38noirbizarre merged 6 commits intonoirbizarre:masterfrom
noirbizarre merged 6 commits intonoirbizarre:masterfrom
Conversation
…ride default prefix
The testserver is not actually running at the non root url so we need to handle the view case differently.
noirbizarre
added a commit
that referenced
this pull request
Jun 27, 2014
Take FORCE_SCRIPT_NAME setting into account
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I routinely deploy Django apps behind a reverse proxy where the root url of the Django app is not "/" e.g.
Public facing server will take requests to http://mysite.com/myapp/ and reverse proxy them to http://localhost:8080/
Django.js does not currently handle this situation (issue #34 appears to be related) without having to resort to manually prefix urls with your script name in your js files. For example if my app is hosted at http://mysite.com/myapp/ then
Django.url('home')will give"/"rather than the desired"/myapp/". This pull request should resolve that.