Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websocket path & django served in subpath #14

Open
jbjuin opened this issue Oct 1, 2020 · 0 comments
Open

Websocket path & django served in subpath #14

jbjuin opened this issue Oct 1, 2020 · 0 comments

Comments

@jbjuin
Copy link
Collaborator

jbjuin commented Oct 1, 2020

Hi Eddy,
I just came across an issue when serving django on a subpath.
The websocket url __reactor__ is hardcoded as /__reactor__ in the frontend.
And I see that you hardcoded django.setup(set_prefix=False) so that the parameter FORCE_SCRIPT_NAME is not used...

So Django is configured to work on a subpath, let's say example.com/app but reactor frontend will try to connect at example.com/__reactor__ and not example.com/app/__reactor__ which should be handled correctly by Django.

Any idea on how to solve that ? A variable passed to js in the template ?

Cheers !

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

No branches or pull requests

1 participant