NGINX dynamic path returning 404
up vote
0
down vote
favorite
i have nginx running locally and am trying to create a simple dynamic path location.
The location block is:
location ~ ^/users/(.+)$/roles {
return 200;
}
After running, I try to hit the endpoint
http://localhost:80/users/1/roles
But I end up with a 404.
If I change the location block to:
location /users/1/roles {
return 200;
}
I get a 200 and everything works just find. I have been pulling my hair out over this because it seems so simple that I thought a ton of documentation would exist about this. But I can not find a solution, any help would be greatly appreciated.
nginx
asked Nov 19 at 20:09
Brennan Batalla
1
add a comment |
up vote
0
down vote
favorite
i have nginx running locally and am trying to create a simple dynamic path location.
The location block is:
location ~ ^/users/(.+)$/roles {
return 200;
}
After running, I try to hit the endpoint
http://localhost:80/users/1/roles
But I end up with a 404.
If I change the location block to:
location /users/1/roles {
return 200;
}
I get a 200 and everything works just find. I have been pulling my hair out over this because it seems so simple that I thought a ton of documentation would exist about this. But I can not find a solution, any help would be greatly appreciated.
nginx
asked Nov 19 at 20:09
Brennan Batalla
1
You seem to have a spurious$in your regular expression. The$is used to anchor the end of a regular expression.
– Richard Smith
Nov 19 at 20:57
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
i have nginx running locally and am trying to create a simple dynamic path location.
The location block is:
location ~ ^/users/(.+)$/roles {
return 200;
}
After running, I try to hit the endpoint
http://localhost:80/users/1/roles
But I end up with a 404.
If I change the location block to:
location /users/1/roles {
return 200;
}
I get a 200 and everything works just find. I have been pulling my hair out over this because it seems so simple that I thought a ton of documentation would exist about this. But I can not find a solution, any help would be greatly appreciated.
nginx
asked Nov 19 at 20:09
Brennan Batalla
1
i have nginx running locally and am trying to create a simple dynamic path location.
The location block is:
location ~ ^/users/(.+)$/roles {
return 200;
}
After running, I try to hit the endpoint
http://localhost:80/users/1/roles
But I end up with a 404.
If I change the location block to:
location /users/1/roles {
return 200;
}
I get a 200 and everything works just find. I have been pulling my hair out over this because it seems so simple that I thought a ton of documentation would exist about this. But I can not find a solution, any help would be greatly appreciated.
nginx
nginx
asked Nov 19 at 20:09
Brennan Batalla
1
asked Nov 19 at 20:09
Brennan Batalla
1
asked Nov 19 at 20:09
Brennan Batalla
1
asked Nov 19 at 20:09
Brennan Batalla
1
asked Nov 19 at 20:09
Brennan Batalla
1
1
You seem to have a spurious$in your regular expression. The$is used to anchor the end of a regular expression.
– Richard Smith
Nov 19 at 20:57
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07
add a comment |
You seem to have a spurious$in your regular expression. The$is used to anchor the end of a regular expression.
– Richard Smith
Nov 19 at 20:57
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07
You seem to have a spurious
$ in your regular expression. The $ is used to anchor the end of a regular expression.– Richard Smith
Nov 19 at 20:57
You seem to have a spurious
$ in your regular expression. The $ is used to anchor the end of a regular expression.– Richard Smith
Nov 19 at 20:57
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381913%2fnginx-dynamic-path-returning-404%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You seem to have a spurious
$in your regular expression. The$is used to anchor the end of a regular expression.– Richard Smith
Nov 19 at 20:57
Thanks, but removing that does not fix it.
– Brennan Batalla
Nov 20 at 16:07