4.3.1 Client Request Buffer

  • Article

The client is requesting property values for specific properties from the server. The first two are named properties and the third one is a standard property. The property IDs for the named properties were gotten from the server by calling the RopGetPropertyIdsFromNames ROP ([MS-OXCROPS] section 2.2.8.1). For more details, see section 4.1 .

A complete RopGetPropertiesSpecific ROP request buffer ([MS-OXCROPS] section 2.2.8.3) is a variable length sequence, with nine required bytes followed by a property tag array. The following example shows the request buffer. 

 0000: 07 00 00 00 00 01 00 03-00 0B 00 3E 86 03 00 3F
 0010: 86 02 01 E2 65

The first three bytes refer to the RopId, LogonId, and InputHandleIndex fields as described in [MS-OXCROPS] section 2.2.

  
 0000: 07 00 00

RopId: 0x07 (RopGetPropertiesSpecific ([MS-OXCROPS] section 2.2.8.3))

LogonId: 0x00

InputHandleIndex: 0x00

The next six bytes of the request buffer are the PropertySizeLimit, WantUnicode, and PropertyTagCount fields as described in section 2.2.2.1.

  
 0003: 00 00 01 00 03-00

PropertySizeLimit: 0x0000. No property size set; maximum limit is default.

WantUnicode: 0x0001. Nonzero means Unicode.

PropertyTagCount: 0x0003. Three property tags in the array.

The remaining bytes constitute the PropertyTags field as described in section 2.2.2.1.

  
 0009: 0B 00 3E 86 03 00 3F 86 02 01 E2 65

PropertyTag1: 0x863E000B (PropertyId: 0x863E->TestProp1, PropertyType: 0x000B-> PtypBoolean)

PropertyTag2: 0x863F0003 (PropertyId: 0x863F->TestProp2, PropertyType: 0x0003-> PtypInteger32)

PropertyTag3: 0x65E20102 (PropertyId: 0x65E2->PidTagChangeKey, PropertyType: 0x0102-> PtypBinary)