How to run with prefix /foo with a remote proxy?

[MIvanchev]

When using wastebin with nginx as reverse proxy I can reach the site through https://<addr>/foo but then all the resources are fetched through https://<addr>. Any way to fix that?

[MIvanchev]

P.S.

wastebin probably needs to support X-Forwared-Prefix.

[matze]

There used to be an option to set a prefix but from a technical standpoint it was too cumbersome to keep. So Forwarded (it's an actual standard header) is probably to the way to do it. But it requires quite a bit of change, so I can't promise anything at this point.

[MIvanchev]

Thanks! That's actually a significant disadvantage IMO if prefixes aren't supported. The cumbersome option is better than nothing.

[matze]

I won't bring back the option but rather extract that info from a Forwarded header.

[MIvanchev]

That'll be perfect, I'm really eager to use it, being and Rust and so simple and straightforward, great work.

[matze]

I think this is not even necessary and it actually stems from using absolute paths in a lot of places. Are you able to test from source?

[MIvanchev]

Sure, if necessary I'll do it.

[MIvanchev]

Yeah, any news on this one, I really need a good paster :))

[ItIsSeven]

Also facing this issue as I wanted to host on a different path behind Nginx

I imagine WASTEBIN_BASE_URL should apply for the JS/CSS files etc. to resolve this issue

[MIvanchev]

Hey @matze I was thinking about this again, isn't the problem solvable through a layer to the router? If you want we could look at it together.

[matze]

The routes themselves are not the problem, I tried exactly what you propose. The problem are URLs that are used in the templates. I tried using relative URLs where possible and it helped to a degree but not always.

[MIvanchev]

Would it help to modify them like this

<link rel="stylesheet" href="{{ page.assets.css.dark.href() }}">

and define the href property to be prefix + route() ?

[MIvanchev]

@matze I'm modding the templates and adding some path prefix, code. Could you tell me what this element is doing and how it should be prefixed?

      <a href="../{{ key }}" class="nav-button" title="paste content" aria-label="paste content">

[MIvanchev]

Hey @matze, I've added some code to support prefixing. The correct header is X-Forwarded-Prefix because Forwarded only carries host info. Let me know what you think.