Redirect

1.1 A note from

{code:none}
#RedirectMatch ^/news(/.*)?$ http://www.ohio.edu/technology/whatsnew/new.cfm
 RedirectMatch ^/intranet(/.*)?$ https://technology.ohio.edu/intranet$1
 RedirectMatch ^/provostmsgbrd(/.*)?$ https://technology.ohio.edu/provostmsgbrd$1
 RedirectMatch ^/preference(/.*)?$ http://technology.ohio.edu/computers/sce/preferences.html
 RedirectMatch ^/development(/.*)?$ https://technology.ohio.edu/development$1
 RedirectMatch ^/go-mobile/secorder(/.*)?$ https://technology.ohio.edu/go-mobile/secorder$1
 RedirectMatch ^/oakguest(/.*)?$ https://technology.ohio.edu/oakguest$1
#RedirectMatch ^/alc(/.*)?$ https://technology.ohio.edu/alc$1
 RedirectMatch ^/p2p/agreement(/.*)?$ https://technology.ohio.edu/p2p/agreement$1
 RedirectMatch ^/alc(/.*)?$ https://technology.ohio.edu/alc$1


{code}

1.1 And a letter I sent


I put these into production and upon first inspection, they seem to work as intended. It worth noting, as we found, that a apache redirect directive will short circuit unless specifically matched. So a statement like:

{code:none}
RedirectMatch ^/internal/       http://www.ohio.edu/audit/internal.cfm
{code}

is really like

{code:none}
/internal/* ->   http://www.ohio.edu/audit/internal.cfm
{code}

if you see some that are inaccurate, I.E. once that need to be exact matches proceeding wild card matches like:

{code:none}
/internal/ ->   http://www.ohio.edu/audit/internal.cfm
/internal/0* ->   http://www.ohio.edu/audit/someotherpage.cfm
{code}

And I didn't put

{code:none}
RedirectMatch ^/internal/$ ->   http://www.ohio.edu/audit/internal.cfm
RedirectMatch ^/internal/0 ->   http://www.ohio.edu/audit/someotherpage.cfm
{code}

Let me know, as I missed it and the first one will override the second one (so I believe)









Comments