Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nginx proxy_pass does not take context_path attribute into account #91

Open
fletchowns opened this issue Sep 19, 2014 · 2 comments
Open

Comments

@fletchowns
Copy link

If node[:nexus][:context_path] is set to "/" instead of the default "/nexus" I would expect https://localhost/ to hit nexus. Instead you get a Jetty error page:

HTTP ERROR: 404
Problem accessing /. Reason:
    Not Found
Powered by Jetty://

Instead you have to go to https://localhost/nexus for it to work.

In the nginx conf if I change proxy_pass http://127.0.0.1:8081/; to proxy_pass http://127.0.0.1:8081/nexus; then it works as I would expect. So I think it's just a matter of incorporating node[:nexus][:context_path] into the nginx conf.

@fletchowns
Copy link
Author

It seems to work as expected after a vagrant destroy && vagrant up. I think the issue is with trying to change the context_path in a subsequent convergence.

@fletchowns
Copy link
Author

@KAllan357 I think it's because the nexus service isn't being restarted when nexus.properties changes. I can't figure out how to get it to do that though using either notifies on the template resource or subscribes on the service resource. Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant