You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 !
The text was updated successfully, but these errors were encountered:
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 parameterFORCE_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 atexample.com/__reactor__
and notexample.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 !
The text was updated successfully, but these errors were encountered: