Tag: Computer Configuration

This policy setting allows you to change the default limit of WebSocket connections per server. The default limit is 6; you can select a value from 2 through 128. If you enable this policy setting Internet Explorer uses the WebSocket connection limit that you set with this policy setting. If you disable or do not configure this policy setting Internet Explorer uses the default limit of 6 WebSocket connections per server.

The WebSocket object allows websites to request data across domains from your browser by using the WebSocket protocol. This policy setting allows administrators to enable or disable the WebSocket object. This policy setting does not prevent client-side communication across domains via other features in Internet Explorer 10. Also this policy setting does not prevent a site from requesting cross-domain data through a server. If you enable this policy setting websites cannot request data across domains by using the WebSocket object. If you disable or do not configure this policy setting websites can request data across domains by using the WebSocket object. By default the WebSocket object is enabled.

This policy setting allows you to choose whether websites can request data across domains by using the XDomainRequest object. Note that this policy setting does not block client-side communication across domains through other features in Internet Explorer 8 and it does not prevent a site from requesting cross-domain data through a server. If you enable this policy setting websites cannot request data across domains by using the XDomainRequest object. If you disable or do not configure this policy setting websites can request data across domains by using the XDomainRequest object.

This policy setting allows you to manage whether documents can request data across third-party domains embedded in the page. If you enable this policy setting documents cannot request data across third-party domains embedded in the page. If you disable or do not configure this policy setting documents can request data across third-party domains embedded in the page.

This policy setting allows you to change the default connection limit for HTTP 1. 0 from 6 connections per host to a limit of your choice (from 2 through 128). If you disable or do not configure this policy setting Internet Explorer will use the default connection limit for HTTP 1. 0 (6 connections per host). In versions of Internet Explorer prior to Internet Explorer 8 the default connection limit for HTTP 1. 0 was 4.

This policy setting allows you to change the default connection limit for HTTP 1. 1 from 6 connections per host to a limit of your choice (from 2 through 128). If you enable this policy setting Internet Explorer uses the connection limit of your choice for HTTP 1. 1. If you disable or do not configure this policy setting Internet Explorer uses the default connection limit for HTTP 1. 1 (6 connections per host). In versions of Internet Explorer before Internet Explorer 8 the default connection limit for HTTP 1. 1 was 2.

This policy setting allows you to hide the reveal password button when Internet Explorer prompts users for a password. The reveal password button is displayed during password entry. When the user clicks the button the current password value is visible until the mouse button is released (or until the tap ends). If you enable this policy setting the reveal password button will be hidden for all password fields. Users and developers will not be able to depend on the reveal password button being displayed in any web form or web application. If you disable or do not configure this policy setting the reveal password button can be shown by the application as a user types in a password. The reveal password button is visible by default. On at least Windows 8 if the “Do not display the reveal password button” policy setting located in Computer Configuration -> Administrative Templates -> Windows Components -> Credential User Interface is enabled for the system it will override this policy setting.

This policy setting allows you to turn off the Data Execution Prevention feature for Internet Explorer on Windows Server 2008 Windows Vista with SP1 and Windows XP with SP3. If you enable this policy setting Internet Explorer does not turn on Data Execution Prevention on platforms that support the SetProcessDEPPolicy function. If you disable or do not configure this policy setting Internet Explorer uses the SetProcessDEPPolicy function to turn on Data Execution Prevention on platforms that support the function. This policy setting has no effect if Windows has been configured to enable Data Execution Prevention.

This policy setting allows you to turn on or turn off Data URI support. A Data URI allows web developers to encapsulate images and . css files within the body of the URL and optionally encode them by using base 64 encoding. Malware filters or other network-based filters may not properly filter encapsulated data. If you enable this policy setting Data URI support is turned off. Without Data URI support a Data URI will be interpreted as a failed URL. If you disable this policy setting Data URI support is turned on. If you do not configure this policy setting Data URI support can be turned on or off through the registry.

This policy setting allows the user to run natively implemented scriptable XMLHTTP. If you enable this policy setting the user can run natively implemented scriptable XMLHTTP. If you disable this policy setting the user cannot run natively implemented scriptable XMLHTTP. If you do not configure this policy setting the user can choose to run natively implemented scriptable XMLHTTP.