Share via

3.4.2.5.8 Sending 403 Forbidden response (Action: Block client with dynamic URL)

  • Article

This section follows the behavior described in product behavior note <174>.

If the server determines that it does not support the version specified in the User-Agent header, it SHOULD respond with a 403 Forbidden error. If the action configured for the version of the client is to block and respond with a dynamic location to download a newer client, the response SHOULD include a Warning header, as specified in [RFC3261] section 7.3.1. The value of the Warning header MUST be constructed as follows:

  • Warn-code is set to the value 312.

  • Warn-agent is set to the value "lcs.microsoft.com".

  • Warn-text is set to the base location to download a newer version of the client. This location is an HTTPS URI and points to a webpage. The URI MUST contain a parameter with the name folder. The server constructs a path relative to this base location, as described in section 3.4.1.5.2. The installers are either Windows Installer (.msi) file or .msp file. The client can automatically install a newer version of the client from this location.

The following is an example of a Warning header with a base HTTPS URL that is sent back in the response.

 Warning: 312 lcs.microsoft.com "https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx?folder=OCv3.1