Full Words in Htaccess Regex
I have the regex [^/]+[^/edit]$ to match URLs and get the string after the last /, unless the string after the last / is edit. However, this regex currently checks for /, e, d, i, and t. How can I have it be a word, and not individual characters? This is for a .htaccess file.
I have a demo setup on Regexr. The goal is to have the first 5 lines matching after the first slash, but the last one not matching at all.
regex .htaccess
asked Nov 14 '18 at 1:47
apxxapxx
14419
add a comment |
I have the regex [^/]+[^/edit]$ to match URLs and get the string after the last /, unless the string after the last / is edit. However, this regex currently checks for /, e, d, i, and t. How can I have it be a word, and not individual characters? This is for a .htaccess file.
I have a demo setup on Regexr. The goal is to have the first 5 lines matching after the first slash, but the last one not matching at all.
regex .htaccess
asked Nov 14 '18 at 1:47
apxxapxx
14419
add a comment |
I have the regex [^/]+[^/edit]$ to match URLs and get the string after the last /, unless the string after the last / is edit. However, this regex currently checks for /, e, d, i, and t. How can I have it be a word, and not individual characters? This is for a .htaccess file.
I have a demo setup on Regexr. The goal is to have the first 5 lines matching after the first slash, but the last one not matching at all.
regex .htaccess
asked Nov 14 '18 at 1:47
apxxapxx
14419
I have the regex [^/]+[^/edit]$ to match URLs and get the string after the last /, unless the string after the last / is edit. However, this regex currently checks for /, e, d, i, and t. How can I have it be a word, and not individual characters? This is for a .htaccess file.
I have a demo setup on Regexr. The goal is to have the first 5 lines matching after the first slash, but the last one not matching at all.
regex .htaccess
regex .htaccess
asked Nov 14 '18 at 1:47
apxxapxx
14419
asked Nov 14 '18 at 1:47
apxxapxx
14419
asked Nov 14 '18 at 1:47
apxxapxx
14419
asked Nov 14 '18 at 1:47
apxxapxx
14419
asked Nov 14 '18 at 1:47
apxxapxx
14419
14419
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
How about the regex: /(?!edit)(?<=/)[a-z-]+$/gm
This combines a positive lookbehind on /, and a negative lookahead on edit, to match any alphanumber characters and hyphens where the string edit is not present:
http://example.com/my-ur // my-ur
http://example.com/my-url-e // my-url-e
http://example.com/my-url-d // my-url-d
http://example.com/my-url-i // my-url-i
http://example.com/my-url-t // my-url-t
http://example.com/edit // [NO MATCH]
This can be seen working on Regexr here.
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
This works on Regexr, but doesn't seem to work on my.htaccessfile. Is there anything here known not to work in htaccess?
– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
add a comment |
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%2f53292035%2ffull-words-in-htaccess-regex%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
How about the regex: /(?!edit)(?<=/)[a-z-]+$/gm
This combines a positive lookbehind on /, and a negative lookahead on edit, to match any alphanumber characters and hyphens where the string edit is not present:
http://example.com/my-ur // my-ur
http://example.com/my-url-e // my-url-e
http://example.com/my-url-d // my-url-d
http://example.com/my-url-i // my-url-i
http://example.com/my-url-t // my-url-t
http://example.com/edit // [NO MATCH]
This can be seen working on Regexr here.
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
This works on Regexr, but doesn't seem to work on my.htaccessfile. Is there anything here known not to work in htaccess?
– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
add a comment |
How about the regex: /(?!edit)(?<=/)[a-z-]+$/gm
This combines a positive lookbehind on /, and a negative lookahead on edit, to match any alphanumber characters and hyphens where the string edit is not present:
http://example.com/my-ur // my-ur
http://example.com/my-url-e // my-url-e
http://example.com/my-url-d // my-url-d
http://example.com/my-url-i // my-url-i
http://example.com/my-url-t // my-url-t
http://example.com/edit // [NO MATCH]
This can be seen working on Regexr here.
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
This works on Regexr, but doesn't seem to work on my.htaccessfile. Is there anything here known not to work in htaccess?
– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
add a comment |
How about the regex: /(?!edit)(?<=/)[a-z-]+$/gm
This combines a positive lookbehind on /, and a negative lookahead on edit, to match any alphanumber characters and hyphens where the string edit is not present:
http://example.com/my-ur // my-ur
http://example.com/my-url-e // my-url-e
http://example.com/my-url-d // my-url-d
http://example.com/my-url-i // my-url-i
http://example.com/my-url-t // my-url-t
http://example.com/edit // [NO MATCH]
This can be seen working on Regexr here.
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
How about the regex: /(?!edit)(?<=/)[a-z-]+$/gm
This combines a positive lookbehind on /, and a negative lookahead on edit, to match any alphanumber characters and hyphens where the string edit is not present:
http://example.com/my-ur // my-ur
http://example.com/my-url-e // my-url-e
http://example.com/my-url-d // my-url-d
http://example.com/my-url-i // my-url-i
http://example.com/my-url-t // my-url-t
http://example.com/edit // [NO MATCH]
This can be seen working on Regexr here.
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
edited Nov 14 '18 at 2:04
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
answered Nov 14 '18 at 1:59
Obsidian AgeObsidian Age
27k72344
27k72344
This works on Regexr, but doesn't seem to work on my.htaccessfile. Is there anything here known not to work in htaccess?
– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
add a comment |
This works on Regexr, but doesn't seem to work on my.htaccessfile. Is there anything here known not to work in htaccess?
– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
This works on Regexr, but doesn't seem to work on my
.htaccess file. Is there anything here known not to work in htaccess?– apxx
Nov 14 '18 at 2:09
This works on Regexr, but doesn't seem to work on my
.htaccess file. Is there anything here known not to work in htaccess?– apxx
Nov 14 '18 at 2:09
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
Hmm, not that I'm aware of sorry. I'm not the most familiar with the specific htaccess side of regexes, but if anything I would assume it's the positive lookbehind. You might be able to make use of RewriteCond backreferences in this regard.
– Obsidian Age
Nov 14 '18 at 2:22
add a comment |
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%2f53292035%2ffull-words-in-htaccess-regex%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
