up vote 1 down vote favorite
share [g+] share [fb]

I've gotten two reports of Outlook freezing since changing the structure of an email I send to use image sources like:

//example.com/file.jpg

instead of:

http://example.com/file.jpg

Is this possible or is it a coincidence (2 reports out of 150k emails - but we've never had this reported before the change)?

link|improve this question
Perhaps Outlook is treating them as UNC paths rather than URLs and freezing during the unsuccessful attempt to access the host as a file server? – Kevin Reid Apr 15 '11 at 0:02
I've confirmed that this will freeze most versions of Outlook. I'm amazed that hackers aren't exploiting this. – Adam Nelson May 19 '11 at 22:36
feedback

migrated from serverfault.com Apr 14 '11 at 20:56

This question came from our site for system administrators and desktop support professionals.

1 Answer

up vote 2 down vote accepted

I've had problems with links like this in Outlook when Internet Explorer is not the default browser. In my case the user had Chrome as the default browser and Outlook was hanging handing over the link to Chrome - it did eventually load the image, but it would take literally 5 minutes of being non-responsive.

Anyway, I would have thought that you really should be specifying the protocol in the hyperlink as best practice, but I'm not sure it will make much difference in this case

link|improve this answer
To be clear, these are attributes in the image tag like this, not hrefs: <img src="//example.com/file.jpg" /> – Adam Nelson Apr 14 '11 at 20:47
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.