You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the README, I would expect the following proxied URLs for the various inputs:
;; wrap-proxy parameters
(wrap-proxy"/remote""http://example.com/base")
;; I would expect the following in -> proxied URL;; http://localhost/remote/hello.html -> ;; http://example.com/base/hello.html;; ;; http://localhost/remote/dir/hello.html -> ;; http://example.com/base/dir/hello.html
This is what I expected going in from the example (I could be wrong) + from my experience with similar functionality in nginx.
To get this example to work, the local base url parameter to wrap-proxyhas to end in a / to the the URI.resolve logic to achieve my expected output:
;; NOTE: /remote/ (trailing slash vs previous)
(wrap-proxy"/remote/""http://example.com/base")
I can submit a patch to meet my expected behavior, but is it the expected behavior?
Appreciate it!
The text was updated successfully, but these errors were encountered:
From the README, I would expect the following proxied URLs for the various inputs:
This is what I expected going in from the example (I could be wrong) + from my experience with similar functionality in nginx.
To get this example to work, the local base url parameter to
wrap-proxy
has to end in a/
to the theURI.resolve
logic to achieve my expected output:I can submit a patch to meet my expected behavior, but is it the expected behavior?
Appreciate it!
The text was updated successfully, but these errors were encountered: