Open tobez opened 5 years ago
wouldn't in your case the mount point be / ?
One would expect this, yes, if not for
my $mount_point = $conf->{mount_point} || '';
$mount_point =~ s{/$}{};
in the caller.
On 15 Mar 2019, at 15:06, Tobias Oetiker notifications@github.com wrote:
wouldn't in your case the mount point be / ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/oetiker/mojolicious-plugin-reverseproxy/issues/6#issuecomment-473298902, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD4v1s8cKMgdecZ27TU5BTIpqCrJ5m2ks5vW6jagaJpZM4b2fWH.
Ping on this one. The bug is still there, and I am still unsure of the "proper" fix. In the meantime, my workaround is to specify
mount_point => '//'
Then the last slash gets stripped, and the mount point really becomes /, and all is dandy.
Hello,
After the commit in question, the URL path is first set to the destination URL path. Then it is set to the request path, but only if mount point is non-empty, which results in insanity like this:
These logs are produced from the following code:
I am not entirely sure how the proper fix would look. I'd probably just remove the line
as obviously non-sensical.