Web config redirects not working where a trailing slash is involved

[AndrewAkesson]

I'm having real trouble with getting working redirects in place to use on a site we're re-launching with a modified url structure.

Old URL: http://www.example.com/example_folder/

New URL: http://www.example.com/example-of-new-folder/

Now, where the old URL's have a trailing slash the web.config simply will not accept it. It says the URL can start with a slash, but not end with a slash. However, many of my URL's do end with a slash so I need a workaround.

These are the rules I'm putting in place:

<location path="example_folder/"></location>

Thanks

[AndrewAkesson]

That works perfectly, thank you very much

[AlanMosley]

The following will work for both slash and no slash,

<rule name="Test" stopprocessing="true"><match url="^example_folder"><action type="Redirect" url="/newfolder"></action></match></rule>

if not sure where to place it, see link in last post, bottom of page

[AndrewAkesson]

Thanks for the response Alan.

However, the problem is with the old URL's, so where they have a trailing slash I cannot get them to redirect to any URL's of the new structure (with a trailing slash or otherwise.).

To simplify the ask, how do I put in place a 301 redirect from 'http://www.example.com/example_folder/' to some other URL?

[AlanMosley]

i would first decide if you want a slash or not. i prefer not as when people type urls they rarly add a slash on the end.

see this page will tell you how to remove all slashes and then your redirects should work

http://thatsit.com.au/seo/tutorials/how-to-fix-canonical-issues-involving-the-trailing-slash