Forum Discussion
Damion_19248
Mar 13, 2013Nimbostratus
I need to apologize for a few things. I realize I wasn't very clear in my specs and I had a typo at the end of my last comment. Both examples should have contained category.htm at the end. I appreciate the help you have given me and I am going to attempt to adjust what you have given me to fit my needs unless you happen to see this and respond before I make something work. I think I have clarified the specs below and will update when I have a working rule in place.
Here are the three conditions.
http://subdomain.domain.com/1050/38745/productdata-reviews/reviews.htm redirected to http://www.domain.com/38745/
In the above example I am only interested in the second set of numbers(38745) in this particular example. The triggering condition needs to be the http::host and the reviews.htm at the end of http::path. The HTTP::host, the 1050 and the reviews.htm at the end of the path are all constant.
http://subdomain.domain.com/1050/38745/productdata-reviews/category.htm Redirect to http://www.domain.com/productdata/
http://subdomain.domain.com/1050/38745/productdata-moredata-reviews/category.htm Redirect to http://www.domain.com/productdata-moredata/
In the above example I am only interested in the third section of the http::path. It may contain a random word which I have shown as productdata or a hyphenated random word shown as productdata-moredata. The third section of the http::path will also contain -reviews which is constant and not needed in the redirected url. The triggering condition needs to be the http::host and the category.htm at the end of http::path.