Opened 2 years ago

Last modified 2 years ago

#3535 new bug

web.conf base configuration not respected. Documented reverse proxy config only works by accidental misconfiguration.

Reported by: ZacharyACoon Owned by:
Priority: major Milestone: needs verified
Component: Web UI Version: 2.1.0
Keywords: web ui reverse proxy base location Cc:


web.conf base set to "/test"

curl deluge_ip/test # FAIL, should be responding here. 404, "No child resource."

curl deluge_ip/ # FAIL, should *not* be responding here. 200 contains links like: <link rel="stylesheet" type="text/css" href="/test/css/ext-all-notheme.css"/>

So the configuration is known by deluge, and it changes the locations of resources for the reverse proxy, but it is not listening at the correct location in the deluge web server.

Change History (1)

comment:1 Changed 2 years ago by ZacharyACoon

to be clear, deluge is basically relying on the reverse proxy to mangle requests.

reverse_proxy/location -> deluge/ (no location)

it *should be*:

reverse_proxy/location -> deluge/location

Note: See TracTickets for help on using tickets.