Hi Nenad, sorry for the delayed reply, I was having email troubles. This worked for me! (of course it was nginx) :)
Thanks! Nick On Thu, Apr 24, 2014 at 2:54 PM, Nenad Merdanovic <[email protected]> wrote: > Hello Nick, > > > I am pretty sure this is an nginx problem, but let's resolve it anyways :) > > On 04/24/2014 12:54 PM, Nick Jennings wrote: > > ... > > > > However when I try to use: > > http://example.com/docs (note: no trailing slash) > > > > I get a long wait, nothing in the nginx logs, and then eventually the > > URL in the browser is rewritten to: example.com:8090/docs > > <http://example.com:8090/docs> and fails. > > I guess you wanted to say: gets rewritten to: example.com:8090/docs/ > > You can prevent nginx from adding a port which breaks this by setting: > port_in_redirect off; [1] > > > > > Any ideas what I've got setup wrong here? Seems pretty straightforward > > to me and I'd like to avoid trying to hack things with redirecting to > > force a slash. Should just work. Initially I thought it was an nginx > > thing, but since I don't even get anything in the nginx logs on the > > second method (/docs) I assume the failure is happening within haproxy. > > Other thing that might fix your issue is to include this in your nginx > configuration: > try_files $uri $uri/ =404; > > This will essentially > > > Thanks in advance for any help! > > -Nick > > > > [1] > http://nginx.org/en/docs/http/ngx_http_core_module.html#port_in_redirect > > Regards, > -- > Nenad Merdanovic | PGP: 0x423edcb2 | Web: http://nimzo.info > Linkedin: http://www.linkedin.com/in/nenadmerdanovic >
