tag:blogger.com,1999:blog-5290934002193555057.post1376769585425163932..comments2022-05-02T08:00:44.233+01:00Comments on Galactic Engineer: Exposing Galaxy reports via nginx in a production instancepjbhttp://www.blogger.com/profile/02877142465318426440noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5290934002193555057.post-61478932437758945732017-03-29T15:48:32.180+01:002017-03-29T15:48:32.180+01:00@DrDave with the caveat that I'm not an expert...@DrDave with the caveat that I'm not an expert in nginx configuration, I believe that the location directive given in the post is correct, i.e.<br /><br />...<br />location ^~ /reports<br />...<br /><br />(note the space between '^~' and '/reports'.)<br /><br />From the nginx documentation for the 'location' directive (see http://nginx.org/en/docs/http/ngx_http_core_module.html#location), '^~' is a modifier which tells nginx not to perform any regular expression matching if this is the best non-regular expression match to the request prefix. As I understand it, in this case it should match any request starting with '/reports'.<br /><br />For your version, the modifier '~' indicates that the expression should be interpreted as a case-sensitive regular expression. So it might produce the same result in practice (but I haven't tried it).<br /><br />HTHpjbhttps://www.blogger.com/profile/02877142465318426440noreply@blogger.comtag:blogger.com,1999:blog-5290934002193555057.post-28726266671600952512017-03-28T14:29:21.822+01:002017-03-28T14:29:21.822+01:00Shouldn't it be ?
...
location ~ ^/report...Shouldn't it be ?<br /> ...<br /> location ~ ^/reports/<br /> ...DrDavehttps://www.blogger.com/profile/06121384702457039518noreply@blogger.com