Bug 17631 – Reverse proxying does not work due to absolute URLs

Bug 17631 - Reverse proxying does not work due to absolute URLs

Summary:

Reverse proxying does not work due to absolute URLs

Status:	UNCONFIRMED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Web Interface
Version:	7.6.1
Platform:	Other Debian Linux

Importance:	-- normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-10-05 16:31 UTC by Mika Fischer
Modified:	2012-12-12 09:26 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Patch to fix absoulte URLs in web interface (23.17 KB, patch) 2011-10-05 16:31 UTC, Mika Fischer	Details \| Diff
Refreshed patch for 7.7.2 (22.84 KB, patch) 2012-12-12 09:24 UTC, Uplink	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mika Fischer 2011-10-05 16:31:06 UTC

Created attachment 7494 [details]
Patch to fix absoulte URLs in web interface

For reverse proxying to work, the web interface may not use absolute URLs. In
many places, "[% webroot %]" etc. is already used. However there are also some
absolute URLs left. Most notably the jsonrpc.js URL which completely kills all
the functionality of the default skin.

The attached patch (against 7.6.1) fixes all absolute URLs I could find and
with it applied, reverse proxying works (at least after quick testing).

Please have a quick look at the changes, as I'm not 100% sure, I've done
everything correctly and apply it if appropriate.

Comment 1 Uplink 2012-12-12 09:24:55 UTC

Created attachment 7695 [details]
Refreshed patch for 7.7.2

Bug still exists in 7.7.2.

It's not just reverse proxying that doesn't work. It's also the alternate /slimserver/ path that is broken (and that path is useful with reverse proxies).

I've refreshed the patch against version 7.7.2, and fixed the diff paths as well (the original patch said HTML.orig, which was wrong).