Re: MSIE 11 HTTP_USER_AGENT

2014-03-31 Thread Claude Schnéegans
Problem is that signature can be faked. Of course, I don't use it to maintain security on my sites, but to insure that pages are displayed correctly. If a visitor using Firefox fakes his signature to look like MSIE, it's his problem. Now if MSIE looks pretends to be Mozilla, it's a problem

Re: MSIE 11 HTTP_USER_AGENT

2014-03-31 Thread Russ Michaels
well there must be some other way to identify or M$ would be screwing themselves on their own sites. On Mon, Mar 31, 2014 at 2:46 PM, wrote: Problem is that signature can be faked. Of course, I don't use it to maintain security on my sites, but to insure that pages are displayed

Re: MSIE 11 HTTP_USER_AGENT

2014-03-31 Thread Andrew Scott
Maybe if one scrolls down to the link http://msdn.microsoft.com/library/ie/hh273397.aspx May explain what Microsoft are doing and saying, I am also sure IE10 also removed most of that infor too. Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+:

Re: MSIE 11 HTTP_USER_AGENT

2014-03-31 Thread Justin Scott
Hi, I discoverd today that MSIE 11 is putting ... Trident/7.0; rv:11.0 still gives it away as IE 11. If you look for that prior to the Mozilla check then it will still catch it properly. -Justin ~| Order the Adobe

Re: MSIE 11 HTTP_USER_AGENT

2014-03-30 Thread Claude Schnéegans
According to this page: http://msdn.microsoft.com/en-us/library/ie/hh869301(v=vs.85).aspx The like Gecko token has been added (for consistency with other browsers). C'mon, how can they talk about consistency with other browsers about a string which is intended to be a signature for all browser?

Re: MSIE 11 HTTP_USER_AGENT

2014-03-30 Thread Andrew Scott
Problem is that signature can be faked. Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/113032480415921517411 On Mon, Mar 31, 2014 at 1:05 PM, wrote: Hi, I discoverd today that MSIE 11 is putting Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0;