Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enabling channels breaks `FORCE_SCRIPT_NAME`
See original GitHub issueHi all!
Today I suddenly figured out that enabling Channels breaks URL “routing” inside Django Admin when FORCE_SCRIPT_NAME is set. I have Django running behind Nginx reverse proxy with /api/ URL prefix. To make Django respect this prefix I set FORCE_SCRIPT_NAME = '/api' in the Django setting file. Everything works fine until I enable Channels by INSTALLED_APPS += ['channels']. After this Django Admin login screen POSTs data the wrong URL, the one without /api/ prefix. If I disable Channels it works fine again. I simply do not know where to dig further. Any help is appreciated.
My setup:
- channels (2.1.0)
- daphne (2.1.0)
- Django (2.0.4)
- Ubuntu Linux 16.04
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey! I’m at the DjangoCon EU sprints. I’m working on this issue.
Looks lovely - thanks for your work on that!