Update a .NET proxy page

Summary

The TLS 1.2 update may cause errors in web apps using proxy pages for the following:

• Accessing cross domain resources.
• Requests exceeding 2048 characters.
• Accessing resources secured with token-based authentication.
• OAuth 2.0 app logins.
• Enabling logging.
• Resource and referrer-based rate limiting.

This article provides detailed steps to update a .NET proxy page.

Procedure

1. Open the browser developer tools and verify if the proxy request status code is 500 Internal Server Error.

2. Verify if the .NET proxy page hosted in Internet Information Services (IIS) uses the .ashx extension.

3. Launch Internet Information Services (IIS) Manager.
4. Navigate to Default Web Site > Proxy. Select Basic Settings to open the Edit Application window.
5. Click Select... to open the Select Application Pool window. Verify the .Net CLR Version is 4.0 and above.

1. Download the latest .NET proxy zip file.
2. Unzip the file and copy the DotNet folder to a temporary folder.
3. Navigate to the path of the current proxy installation files. Open proxy.config and copy all content within the <serverUrls> and </serverUrls> tags.

4. Navigate to the new DotNet folder and open the proxy.config file.
5. Replace the contents within the <serverUrls> and </serverUrls> tags with the content copied in Step 3.
6. Backup the current proxy installation.
7. Replace all the files within the proxy installation directory with the new modified files.
8. Test the proxy page with the following command:

http://<webserver>/proxy/proxy.ashx?ping

9. Test the web app.