RegEx captures path, even though I’m not telling it to
-
I’ve got a redirect set up with a regular expression that looks like this:
^/technology/?.*
Notice, no parens.
It 301 redirects to this:
https://www.shu.edu/technology/news/index.cfm
Notice, no $1.
But what happens is, it redirects to this:
Which of course generates a 404 error. Why is it grabbing the path and doing a rewrite?
In the short term I’m going to add a trailing slash after …cfm, but that’s a kludge. I’d love to know what’s going on.
The page I need help with: [log in to see the link]
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- The topic ‘RegEx captures path, even though I’m not telling it to’ is closed to new replies.
