Setup Configuration

Setup configuration requires administrator privileges and is persistent across restarts. Typically, a setup application running with administrator privileges performs such persistent configuration during setup so that applications can then run at lower privilege, though persistent configuration may be done at any time. Setup configuration can include any of the following four activities:

• Creating a URL reservation. The HTTP API enables the setup application to reserve URL prefixes for request queues associated with specific applications. To reserve a URL, the setup application calls the HttpSetServiceConfiguration function with ConfigId parameter set to HttpServiceConfigUrlAclInfo and passes a pointer in the pConfigInformation parameter to an HTTP_SERVICE_CONFIG_URLACL_SET structure containing the registration information. For more information, see Namespace Reservations, Registrations, and Routing.
• Configuring SSL. To configure SSL, the administrator calls the HttpSetServiceConfiguration function with ConfigId parameter set to HttpServiceConfigSSLCertInfo and passes a pointer in the pConfigInformation parameter to an HTTP_SERVICE_CONFIG_SSL_SET structure containing the SSL certificate information.
• Setting other HTTP server–wide, persistent configurations, such as the IP addresses on which the HTTP server will listen and the server-wide timeout value. See IP Listen List and HTTP_SERVICE_CONFIG_TIMEOUT_SET.