2.1 Transport
The Windows Updated Services: Server-Server Protocol operates over the following transports:
Web Services: SOAP 1.1 ([SOAP1.1]) or SOAP 1.2 ([SOAP1.2-1/2003] and [SOAP1.2-2/2003]) over HTTP or HTTPS over TCP/IP ([RFC2616])
USS Content Download: HTTP over TCP/IP ([RFC2616])
The web services MUST operate on the following URI endpoints.
|
Web service |
Location |
|---|---|
|
http://<server>:<server port>/ServerSyncWebService/ServerSyncWebService.asmx |
|
|
http://<server>:<server port>/ dssauthWebService/dssauthWebService.asmx |
|
|
Reporting Web Service |
http://<server>:<server port>/ReportingWebService/ReportingWebService.asmx |
Each web service MUST be bound to the HTTP transport, as specified in the following Web Services Description Language (WSDL) element.
-
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
Each web service MUST support SOAP over HTTP, as specified in [RFC2616]. Each Web service SHOULD support HTTPS for securing its communication with clients.<3>
To optimize network bandwidth, the DSS MAY request that the reply be compressed by specifying the encoding format in the HTTP Accept-Encoding request-header field (as specified in [RFC2616] section 14.3).<4> The USS SHOULD compress the reply in the requested format.
USS Content Download
The USS Content Download MUST operate on the following URI endpoints.
http://<server>:<server port>/Content/<folder name>/<content file name>
where:
<server> is the IP address or FQDN of the USS.
<server port> is the TCP/IP port on which the USS supports this protocol.
<folder name> is the last two hexadecimal digits of the SHA1 hash for the file to be downloaded. The SHA1 hash is sent down in the GetUpdateData (section 3.1.4.6) call.
<content file name> is the name of the content file.
The following rules MUST be applied to the configuration of the USS Content Download transport based on the configuration of the USS Web Services transport:<5>
If USS Web Services uses HTTP, USS Content Download uses HTTP over TCP port 80.
If USS Web Services uses HTTPS over TCP port 443, USS Content Download uses HTTP over port 80.
If USS Web Services uses HTTPS over TCP port N, where N is not 443, USS Content Download uses HTTP over port N–1.
A USS Content Download SHOULD<6> support HTTP 1.1 Byte Range requests, as specified in [RFC2616] section 14.35. The downloaded content files are binary.