Url Tracker not working on v7.1.4 with versions 2 or 3 - not redirecting manually entered 301s
We can't seem to get the URL Tracker working on v7.1.4. We had version 2.5.(3?) installed and just upgraded to 3.0.1.
When we manually add redirects to the tracker and then hit the url (i.e. /test/ redirect to homepage), we are just brought to a 404 page instead of being 301 redirected to the correct page.
Are there any IIS / web.config settings that need to be manually configured for this package to work in v7? Are there any known conflicts with v7?
We've used this package on several v6 and v4 sites and it has worked flawlessly. We love this package and are a bit stumped as to why we can't get it to work in v7.
Here's the scoop. We tried this with and without the hostnames bound yesterday to no avail. Based on your response, I tried again today and found out that the hostname www.test.com won't work, but http://www.test.com or https://www.test.com will work.
That brings me to another issue. Our entire site requires https, so we have a simple Application_BeginRequest http to https redirector. It simply checks if the request is secure and if not, changes the http:// protocol to https://.
We bound our site in Umbraco to www.test.com and https://www.test.com (the latter makes the Url Tracker work).
Now when we setup a redirect rule, it's redirecting to port 8443. For example, for Root Node: https://www.test.com Old Url: url-redirect-test/ Redirect node: Homepage Redirect type: Permanent 301 Forward query string: Yes
Url Tracker not working on v7.1.4 with versions 2 or 3 - not redirecting manually entered 301s
We can't seem to get the URL Tracker working on v7.1.4. We had version 2.5.(3?) installed and just upgraded to 3.0.1.
When we manually add redirects to the tracker and then hit the url (i.e. /test/ redirect to homepage), we are just brought to a 404 page instead of being 301 redirected to the correct page.
Are there any IIS / web.config settings that need to be manually configured for this package to work in v7? Are there any known conflicts with v7?
We've used this package on several v6 and v4 sites and it has worked flawlessly. We love this package and are a bit stumped as to why we can't get it to work in v7.
Any help would be much appreciated.
Have you configured hostnames by any chance?
Thanks for the quick response Stefan.
Here's the scoop. We tried this with and without the hostnames bound yesterday to no avail. Based on your response, I tried again today and found out that the hostname www.test.com won't work, but http://www.test.com or https://www.test.com will work.
That brings me to another issue. Our entire site requires https, so we have a simple Application_BeginRequest http to https redirector. It simply checks if the request is secure and if not, changes the http:// protocol to https://.
We bound our site in Umbraco to www.test.com and https://www.test.com (the latter makes the Url Tracker work).
Now when we setup a redirect rule, it's redirecting to port 8443. For example, for
Root Node: https://www.test.com
Old Url: url-redirect-test/
Redirect node: Homepage
Redirect type: Permanent 301
Forward query string: Yes
Upon hitting http://www.test.com/url-redirect-test/ or https://test.com/url-redirect-test/ we are redirected to https://www.test.com:8443
Any idea why the port is being set to 8443? It appears to be happening in the Url Tracker.
Thanks again!
Zac
Could you create an issue at Github with the information from this ticket?
https://github.com/kipusoep/UrlTracker/issues
Thanks in advance!
Of course - thank you!
https://github.com/kipusoep/UrlTracker/issues/22
Thanks - the port issue turned out to not be a url tracker issue.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.