Share via

3.3.5.2.7 Handling Compounded Requests

  • Article

If the NextCommand field in the SMB2 header of the request is not equal to 0, the server MUST process the received request as a compounded series of requests. The server MAY<265> fail requests in a compound chain which require asynchronous processing.

There are two different styles of compounded requests, which are described in the following subsections.

If each request in the compounded request chain, except the first one, does not start at an 8-byte aligned boundary, the server SHOULD<266> disconnect the connection.

The two styles MUST NOT be intermixed in the same transport send, and in such a case, the server SHOULD<267> fail each of the requests with STATUS_INVALID_PARAMETER.