Yes I know, but a single case is not enough for me to consider chaning this. You can do it yourself though, because it's open-source and all the bits are available on Github.
If you do change this yourself, it would be nice to receive a pull-request with that changes.
Also I can't remove the port number, because it's a valid part of a URL and can be different than 80.
Port Number in URL
Hi, we've got the tool working however when it redirects pages, the URL it creates has the port number in it, and doesn't work.
For example redirecting to "/example/page1" gives us the URL:
http://www.website.com:87/example/page1
Are we missing a setting or something?
Do you have hostnames with port 87 configured? Or are you running the website on port 87?
Our domain names do not contain the :87, but we have a webfarm and our sites run off different ports, this one being 87.
Hmm I don't have any experience with this particular situation, so I'm not able to help with it I'm afraid...
Well, I realise this is a different tool, but looking at the below post, it could be to do with the way you grab the URL to build your redirect url:
http://our.umbraco.org/projects/website-utilities/tweet-on-publish/misc/8328-The-URL-posted-contains-the-80-port-number
"took out the u.Port in the baseurl"
Is this possible?
Yes I know, but a single case is not enough for me to consider chaning this. You can do it yourself though, because it's open-source and all the bits are available on Github.
If you do change this yourself, it would be nice to receive a pull-request with that changes.
Also I can't remove the port number, because it's a valid part of a URL and can be different than 80.
I have the same problem.
My configuration:
I had to roll back any changes so I lost a lot of time.
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.