Hi,
I have this rule in my nginx config file
location ~* \/(fileA.txt|fileB.txt)$ {
return 404 'nothing here';
}
but it’s not working
but
location /fileA.txt {
return 404 'nothing here';
}
is working…
Any idea what’s wrong ?
Thanks.
You must log in or register to comment.
You might have another location block before it that catches the route.
I ran into something similar and the docs didn’t make sense. This link helped figure things out.
Thank you @ramble81@lemmy.zip 👍
Post saved !
You aren’t escaping your periods. Try like this:
location ~* \/(fileA|fileB)\.txt$ { return 404 'nothing here'; }Thanks @elbucho@lemmy.world
I’ve tried
location ~* \/(fileA\.txt|fileB\.md)$ { return 404 'nothing here'; }but still not matching :'(
.md or .txt?
.md is correct, it’s a test.
Never mind, I understood my mistake… This nginx built didn’t come with ngx_http_rewrite_module so return will not works.Apparently ngx_http_rewrite_module “module” is installedby default with nginx… damn thay should use diffrent terms for what could be install or not at compile time…
Actually I don’t think the error lay in the regex.
because
location /fileA.txt { return 404 'nothing here'; }Does not works either…
Finally it works as it should I update my old nginx version to newest freenginx and read Thoroughly the
locationdocumentation and this post thanks to @ramble81@lemmy.zip