MagneticoW is currently not reverse-proxiable out-of-the-box from a sub-path. Some URIs are relative, others absolute. No environment variable nor configuration setting may allow us to specify a "public URL" or even a "base path" to make the internal Go router generate correct URLs.
Although, it's possible to come up with proper NGINX's sub_filter or Apache's proxy_html/substitute modules usages to fix them.
This patch back-ports @rnhmjoj's "fix" to avoid crash when extracting hash from URL on /torrents/{{ hash }} page.
MagneticoW is currently not reverse-proxiable out-of-the-box from a sub-path. Some URIs are relative, others absolute. No environment variable nor configuration setting may allow us to specify a "public URL" or even a "base path" to make the internal Go router generate correct URLs. Although, it's possible to come up with proper NGINX's
sub_filter
or Apache'sproxy_html
/substitute
modules usages to fix them. This patch back-ports @rnhmjoj's "fix" to avoid crash when extracting hash from URL on/torrents/{{ hash }}
page.