Mixing
How do I look for a file on disk that matches a regex? (e.g. /123-foo serves up /123-bar.html)
Is it possible to dynamically look up file names as part of try_files or some other directive?
I want to have 123-bar.html in my directory, and have it served up to any URL that is prefixed with 123. So 123-foo, 123-baz etc should all match it. I know how to make it work hard-coded, but I'm wondering if there's some way to regex match the file names that get served up.
nginx
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
add a comment |
Is it possible to dynamically look up file names as part of try_files or some other directive?
I want to have 123-bar.html in my directory, and have it served up to any URL that is prefixed with 123. So 123-foo, 123-baz etc should all match it. I know how to make it work hard-coded, but I'm wondering if there's some way to regex match the file names that get served up.
nginx
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14
add a comment |
Is it possible to dynamically look up file names as part of try_files or some other directive?
I want to have 123-bar.html in my directory, and have it served up to any URL that is prefixed with 123. So 123-foo, 123-baz etc should all match it. I know how to make it work hard-coded, but I'm wondering if there's some way to regex match the file names that get served up.
nginx
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
Is it possible to dynamically look up file names as part of try_files or some other directive?
I want to have 123-bar.html in my directory, and have it served up to any URL that is prefixed with 123. So 123-foo, 123-baz etc should all match it. I know how to make it work hard-coded, but I'm wondering if there's some way to regex match the file names that get served up.
nginx
nginx
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
asked Jan 2 at 17:27
Pat MaddoxPat Maddox
1
1
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14
add a comment |
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f54010648%2fhow-do-i-look-for-a-file-on-disk-that-matches-a-regex-e-g-123-foo-serves-up%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
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.
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%2f54010648%2fhow-do-i-look-for-a-file-on-disk-that-matches-a-regex-e-g-123-foo-serves-up%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
Not with plain Nginx. You may be able to search directories using LUA or Perl extensions.
– Richard Smith
Jan 3 at 9:44
Okay thanks for that. One problem I realized is that multiple URLs would serve a 200 for the same content, which I think search engines don't like. My approach now is to construct a redirects named location as part of the site build: location / { try_files $uri/index.html $uri.html $uri =404; } location ~ /(d+)-.*$ { try_files $uri/index.html $uri.html $uri @redirects; } location @redirects { rewrite /123-.*$ /123-super-chicken permanent; }
– Pat Maddox
Jan 4 at 18:14