When clicking (or CTRL+clicking) a link in Microsoft Word 2010 (likely affecting other versions) that requires prior authorization, I'll frequently end up being pointed to an invalid URL. Theoretically, this is an issue with both Word and the service provider's own redirect, but I believe the issue is fundamentally with Word.
I've noticed that there is a delay of 1s-2s after clicking. It appears that Word is validating the link prior to opening my default browser. This is a problem because it also appears to be following the 301/302 redirect internally prior to opening the browser and instead opens the redirected URL instead of opening the browser using the originally specified URL.
- Lag when clicking (or CTRL+clicking) links in Microsoft word.
- Website links which require authorization and redirect will result in opening default browser on the redirected page URL instead of the originally intended URL. If the site doesn't cleanly/transparently incorporate the return URL in the login page URL, it will effectively result in you not visiting to the intended page.
- Servers which return a 500 or 403 error may be completely denied access, when all I want is for it to open in Chrome/Firefox/etc. This happens by presenting an error alert/dialog without ever leaving Word itself.
This particularly affects links which require authorization. For example, I found a URL on superuser.com that requires authorization and redirects if not authorized. The end result is you never get to the intended URL. While this is an error in superuser's redirect, the fundamental issue lives within Word.
- Link pasted into Word: https://superuser.com/users/preferences/
- In the background, processes this URL and, naturally because it or Internet Explorer is not logged in, it receives a response to visit: https://superuser.com/users/login?ssrc=user_prefs&returnurl=http%3a%2f%2fsuperuser.com%2fusers%2fpreferences%2f0
- Finally, since thankfully superuser.com knows I'm already logged in, it follows
returnurlwhich unfortunately is still not valid: https://superuser.com/users/preferences/0
Another authorization example which demonstrates unclean redirect behavior is JIRA. This happens even if you're already authorized/logged in.
- Link pasted into word: https://INSTANCE.atlassian.net/browse/ISSUE-1234
- Word opens this URL: https://INSTANCE.atlassian.net/login?dest-url=%2Fbrowse%2ISSUE-1234&permission-violation=true
- Even though you're logged into JIRA, you will not be redirected to the originally intended URL so your journey ends here.
How do I disable this or is it even possible to workaround at all?