3.2.5.11 Receiving a Log Request

The server MUST first follow the steps defined in section 3.2.5.1.

The server SHOULD communicate the logging information submitted by the client to the higher layer.

The server SHOULD validate the syntax of the fields as specified in [MS-WMLOG]. Server-specific implementations determine how to treat malformed logs submitted by the client.<74>

If the value of the Client-Token variable in the abstract data model is "WMCacheProxy", and the server receives a rendering log (as specified in [MS-WMLOG] section 2.7), it SHOULD forward the rendering log to the origin server.

If the value of the Client-Token variable in the abstract data model is "WMCacheProxy", and the server receives a streaming log (as specified in [MS-WMLOG] section 2.6), it SHOULD NOT forward the streaming log to the origin server.

If the value of the Client-Token variable in the abstract data model is "WMCacheProxy", and the server legacy log (as specified in [MS-WMLOG] section 2.5), it SHOULD NOT forward the legacy log to the origin server, but SHOULD extract the rendering log information and forward that information to the origin server as a rendering log.

The Log response MUST follow the rules in sections 3.2.5.2 and 2.2.2.4.

If the value of the Session-State variable is STREAMING and the value of the Request-Connection variable is equal to the value of the Data-Connection variable, the server MUST continue sending $D packets and MUST add the Log response to the tail of the list in the Pending-Responses variable.

If the server does not add the Log response to the Pending-Responses variable, then the server MUST send the Log response.