2.2.4.45 OUT_R2/C1 RTS PDU
The OUT_R2/C1 RTS PDU MUST be sent from the client to the outbound proxy as part of the OUT_R2 protocol sequence to fill up the predeclared content length for the OUT channel HTTP request defined in section 2.1.2.1.2.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RTS Header (20 bytes) |
|||||||||||||||||||||||||||||||
... |
|||||||||||||||||||||||||||||||
... |
|||||||||||||||||||||||||||||||
EmptyOrPadding (variable) |
|||||||||||||||||||||||||||||||
... |
RTS Header (20 bytes): See section 2.2.3.6.1. The Flags field of the RTS Header MUST be the value RTS_FLAG_PING. The NumberOfCommands field of the RTS Header MUST be the value 1.
EmptyOrPadding (variable): MUST be an Empty command or a Padding command. This RTS PDU MUST be exactly the same size as OUT_R1/A11. Whichever of the two commands produces the desired PDU size MUST be used. If the Padding command is used, the value for the ConformanceCount field MUST be chosen such that PDU has a size equal to the size of OUT_R1/A11. The Empty command format is defined in section 2.2.3.5.8. The Padding command format is defined in section 2.2.3.5.9.