-
Notifications
You must be signed in to change notification settings - Fork 4
Virtual_PATH, Added trailing '/' to proxy_pass #1
base: multiple-paths
Are you sure you want to change the base?
Conversation
* Require `dict` and `sha1` function support in docker-gen
Currently uses the same htpasswd for all services behind a hostname, but it could be desirable to allow different htpasswd for different paths
Multiple paths
…ule was required to redirect to root /
Does this work with subpaths of Assuming that subpaths work correctly, I'm still not sure this is the right default behavior, since I could see this being a matter of user preference. Do you mind bringing up the issue over at nginx-proxy#47 where there can be more visibility? Only you and I are likely to ever see this PR. |
BTW, this branch is being occasionally rebased against the |
i didn't try it against subpaths of VIRTUAL_PATH, i only needed to route I placed the PR against your branch because I wasn't sure how to generate On Thu, Mar 26, 2015 at 2:01 PM, Mike Dillon [email protected]
|
Placing a PR against my branch is appropriate. I just wanted to give you a heads-up since I saw that your PR contains commits from the upstream |
Just verified that it'll work for request paths like /admin/foo -- which I'll update nginx-proxy#47 with the information. Thanks. On Thu, Mar 26, 2015 at 2:10 PM, Mike Dillon [email protected]
|
I'm guessing that's not the behavior most people would want. I can imagine two behaviors that I would expect users to want:
I don't think that rewriting all requests from The other thing I wonder about is whether this has any effect on query strings. |
From my research, which lead me to finding the missing slash, it appears But, reading over the comments in the original Issue, I felt that most just On Thu, Mar 26, 2015 at 4:10 PM, Mike Dillon [email protected]
|
also - just to clarify. If i set VIRTUAL_PATH=/admin: if I set VIRTUAL_PATH=/admin/v1 On Thu, Mar 26, 2015 at 4:16 PM, Josh Swann [email protected] wrote:
|
Cool. So that sounds like what I described in the second option. 👍 I'm still not sure what other users would expect the default behavior to be for |
I would really like to use this feature! anything I can do to help get it merged? |
Not sure. I've just been using the branch in my repo. I think @md5 has been waiting on the jwilder project before rebasing and merging all changes in |
Thanks for the update @jswann ! |
@WillBeebe Are you specifically looking for this trailing slash fix (which I'm still not convinced is a good idea as default behavior), or are you talking about getting a new PR for the In terms of further discussion, I'd like to see that over at nginx-proxy/docker-gen#47 (though I did just comment here too: nginx-proxy#190 (comment)) |
Hi @md5 . I was mostly looking for VIRTUAL_PATH support. Here is a modified nginx.tmpl that I used to do this. Most notably I had to add $host to this line: https://gist.github.com/WillBeebe/0186bae3ac20f6354819#file-gistfile1-txt-L160 |
My goal is to have an nginx container auto-detect and route to separate rails containers. Here's my docker-compose.yml. Running |
Adjust entrypoint to always warn on missing socket
6b2e0cf
to
f2ec4b8
Compare
f7d9156
to
edfedca
Compare
@WillBeebe, Can you confirm that your modified nginx.tmpl is stable? Issues since 9 months? Thanks in advance!! |
Hei guys, I am looking to do something like this. Nginx proxy -> multiple apps as the following:
My Nginx config will look something like this.
I am not really sure whether the fix in this PR is for this use case. If yes, that will be great. Let me know if this is a separate issue that needs to be addressed on its own. Thanks!!! |
@jagandecapri The main discussion around supporting your use case is over at nginx-proxy#47. The most recent PR I created to support multiple paths is at nginx-proxy#254, although it is not in a state to be merged. There is also related discussion in nginx-proxy#54 and nginx-proxy#190. My feeling is still that a custom |
For me to successfully get Virtual_Path's to work, I had to add a trailing slash (/) to the proxy_pass url. Otherwise the proxy would append the path when proxying requests.