http-browserdetect
http-browserdetect copied to clipboard
Is BrowserDetect supposed to distinguish email clients?
The following user agent is from MS Outlook opening a URL (fetching an image for display within an email):
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2; .NET CLR 1.1.4322; Tablet PC 2.0; OfficeLiveConnector.1.5; OfficeLivePatch.1.3; .NET4.0C; .NET4.0E; CMLSATL; Microsoft Outlook 15.0.4719; Microsoft Outlook 15.0.4719; ms-office; MSOffice 15)
It is detected only as os=windows browser=ie browser_version=7.0.
The browscap database identifies this as Outlook 2013, so it is possible. I don't know if it is the goal here, however, so I am unsure if this is a bug or a feature enhancement :)
Here's what we're currently detecting:
http://www.browserdetect.org/?ua=Mozilla%2F4.0+%28compatible%3B+MSIE+7.0%3B+Windows+NT+6.1%3B+Trident%2F7.0%3B+SLCC2%3B+.NET+CLR+2.0.50727%3B+.NET+CLR+3.5.30729%3B+.NET+CLR+3.0.30729%3B+Media+Center+PC+6.0%3B+InfoPath.2%3B+.NET+CLR+1.1.4322%3B+Tablet+PC+2.0%3B+OfficeLiveConnector.1.5%3B+OfficeLivePatch.1.3%3B+.NET4.0C%3B+.NET4.0E%3B+CMLSATL%3B+Microsoft+Outlook+15.0.4719%3B+Microsoft+Outlook+15.0.4719%3B+ms-office%3B+MSOffice+15%29
We don't currently detect email clients, but this seems like it might be worthwhile to add. @dougwilson, thoughts?
I'm indifferent regarding this type of detection, but I can say that the (older) Outlook rendering engine was technically some weird MS Word rendering thing, which would be good to know.
Awww. I wanted to check if there was any change to this with the newest release, and I find that the browserdetect.org domain is now expired.
@khera I'll get it back online tonight. Was on my todo list. Thanks for the poke.
browserdetect.org is back online now.