Hi All,
Quick Q: Why does the following config not work ie NginX is returning a
404 when I attempt to access a php file/page from the "/common/" location?
Obviously I'm misunderstanding something about how location directives
work :-)
~~~
location /common/ {
root /www;
try_files $uri $
Thank you for your answer! I read the paragraph. I changed the preceding
modifier to ~* and it works now.
I made a mistake addressing the OR condition and calling it regex sorry.
Thank you for your help!
> On Wed, Mar 26, 2014 at 04:44:49PM -, Alex wrote:
>
> Hi there,
>
>> location ^~ /(v
Wow Francis.
You are a patient man. I love the way you teach things. I mean it all.
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wed, Mar 26, 2014 at 04:44:49PM -, Alex wrote:
Hi there,
> location ^~ /(videos|events) { #it does not work. So I assume is the OR
> that does not work.
>
> Any thoughts?
The documentation is at http://nginx.org/r/location.
It's all useful, but the fourth sentence is particularly relev
Francis -
What I meant was that I was using an OR statement as it is used in the jpg
example. If I do this:
location ^~ /videos/ { # it works
location ^~ /(videos|events) { #it does not work. So I assume is the OR
that does not work.
Any thoughts?
Thanks,
Alex
> On Wed, Mar 26, 2014 at 12:
On Wed, Mar 26, 2014 at 12:31:30PM -, Alex wrote:
Hi there,
> This OR regex : location ~* \.(gif|jpg|jpeg)$
Which part of that line says that it is a regex?
(The answer is in the documentation.)
> works on jogs and gifs, why can not I use the same syntax for the URIs as
> I am doing it?
Francis -
Thank you for your reply!
This OR regex : location ~* \.(gif|jpg|jpeg)$
works on jogs and gifs, why can not I use the same syntax for the URIs as
I am doing it?
Does it mean then that I have to define each location block one by one
with different URIs even though all the information
Francis -
Thank you for your reply!
This OR regex : location ~* \.(gif|jpg|jpeg)$
works on jogs and gifs, why can not I use the same syntax for the URIs as
I am doing it?
Does it mean then that I have to define each location block one by one
with different URIs even though all the information
On Wed, Mar 26, 2014 at 12:30:21AM -, Alex wrote:
Hi there,
> It works only when I include
> one item, when I do (videos|events) it does not work
>
> location ^~ /(videos|events) {
That is not a regex location. A request for /videos/ will not match it.
http://nginx.org/r/location
I set up two upstream servers (server 1 and server 2) where I geotarget
people from specific countries: A
People from country A go to server 1 and the others go to server 2.
There are some uri s that must be served by server 1 when the person is in
country A. So I have created this directive. It
10 matches
Mail list logo
