-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeviceCPU returning Unknown for 32-bit IE on 64 bit OS #21
Comments
I updated the DeviceCPU. |
I have chosen to ignore the application architecture for the simple reason that I do not see any useful applications of such a field and it seems to be available in only a very limited number of situations. |
So, for your information the primary use case is this:
Historically at least, the 32-bit version of IE has a higher level compatibility especially with add-ons . I guess it's still the case, as it's the default mode for IE 11. The 64-bit mode provides greater access to memory, and apparently is more secure. I think with Edge, you get the 64-bit version of the browser if you're on a 64-bit machine, and the 32-bit version only if you're on a 32-bit machine. |
Hi,
I noticed that with this user agent string:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.3; .NET4.0E)
When I ask for UserAgent.getValue("DeviceCpu"), I get a value of Unknown. From the MSDN docs you found:
So, maybe it could be updated?
Also, I guess DeviceCPU is intended to show the CPU of the device, but really the user agent string (at least in this example) tells us two things:
Maybe as a future enhancement, DeviceCPU could be supplemented with another entry that indicates Agent architecture? Just a thought.
The text was updated successfully, but these errors were encountered: