Browser returns error code 37 when accessing an Apache site via Unified Access Gateway using HTTP 1.0

Article ID: 2678886 - View products that this article applies to.
Expand all | Collapse all

Symptom

Consider the following scenario:

1. An Apache-based application is published by Microsoft Forefront Unified Access Gateway 2010 (UAG) using the "Other Web Application" template.

2.  A user attempts to access the application from a browser that use HTTP/1.0.

In this scenario, the backend application will reply back with “connection: close” and will terminate the SSL connection with close_notify. UAG, instead of sending that reply back to the client, will either send back a 500.htm error or Error 37: "An unknown error occurred while processing the certificate".

Cause

UAG does not support a client browser sending HTTP 1.0 with an Apache backend when the Apache server is setup to use HTTP 1.0.  

Resolution

To work around this issue, enable HTTP 1.1 on the client browsers.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2678886 - Last Review: August 27, 2012 - Revision: 3.0
Applies to
  • Microsoft Forefront Unified Access Gateway 2010
Keywords: 
KB2678886

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com