Share via

3.4.1.5.2 Construction of Dynamic URL

  • Article

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

In the cases where a dynamic URL is sent back, as described in section 3.4.2.5.8 and section 3.4.2.5.9, the user agent constructs an HTTPS URL based on the base URL by adding the following possible parameters:

  • lang: The language of the UAC that needs to be installed. Possible values are the values specified in the first and third columns of the table in section 3.4.1.5.3.

  • arch: The architecture of the UAC that needs to be installed. Possible values are "x32" and "x64".

  • flavor: The flavor of the UAC that needs to be installed. Possible values are the following:

    • pm: Per computer.

    • pu: Per user.

  • Build: The type of build that needs to be installed. Possible values are the following:

    • fre: A free or retail build.

    • chk: A checked or debug build.

The following is an example of the Warning header that contains the base HTTPS URI:

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

The following is an example of the URL a UAC might construct from the preceding base HTTPS URI to download a newer UAC:

 Warning: 312 lcs.microsoft.com https://fabrikam.com/AutoUpdate/Int/Handler/update.aspx?folder=OCv3.1&lang=en-us&arch=x32&flavor=pu&build=fre