Skip to content

Take FORCE_SCRIPT_NAME setting into account#38

Merged
noirbizarre merged 6 commits intonoirbizarre:masterfrom
randlet:force-script-name
Jun 27, 2014
Merged

Take FORCE_SCRIPT_NAME setting into account#38
noirbizarre merged 6 commits intonoirbizarre:masterfrom
randlet:force-script-name

Conversation

@randlet
Copy link
Contributor

@randlet randlet commented Jun 11, 2014

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.

noirbizarre added a commit that referenced this pull request Jun 27, 2014
Take FORCE_SCRIPT_NAME setting into account
@noirbizarre noirbizarre merged commit b0b067a into noirbizarre:master Jun 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants