Skip to content

Websocket path & django served in subpath #14

@jbjuin

Description

@jbjuin

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 !

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions