Description of Windows Azure Pack Web Sites v2 Update 1

Issue 1

The Web Site Controller role slowly leaks memory when during a repair of another server in the system. The severity of the problem depends on the number of roles in the system. When this issue occurs, it could cause the controller role process to restart.

Note This problem does not affect the operation of hosted websites. However, it may delay changes or repairs to the website cloud roles.

Issue 2

Proxy settings do not support setting a bypass list for the proxy settings that are contained in the hosting configuration. This may cause problems when you deploy an instance of Windows Azure Pack Web Sites in a proxy configuration.

Issue 3

The upgrade process requires manual steps for deployments that have multiple controllers. Additionally, the upgrade process does not support high-availability during an upgrade.

Feature 1

The X-Powered header is removed.

Note The X-Powered header provides information that helps identify the technology that is used by a website. Removal of the X-Powered header makes the website less vulnerable to malicious attacks.

Feature 2

Adds ISAPI/Classic mode as a Web Sites capability. This mode is in addition to the existing integrated mode.

Note ISAPI/Classic mode lets you host older ASP.NET applications that run as iSAPI extensions.

Feature 3

Adds virtual directory functionality.

Note A virtual directory maps to a physical location on a hard disk and is represented by a virtual path within the application URL namespace. For example, a virtual directory that has a virtual path of “/vdir” may be represented by the following URL:

http://www.mysite.com:81/app1/vdir

Feature 4

Adds NTLM and Kerberos integration for websites on Windows Azure Pack Web Sites with Active Directory. This lets you use Active Directory authentication and authorization for websites. Earlier versions do not support pass-through authentication.

Feature 5

Adds integration between Active Directory web application users and SQL Server. This lets you use the website user identity when SQL Server databases are accessed.

Note This feature does not yet work for PHP-based websites.