diff options
| author | Ralph Boehme <slow@samba.org> | 2019-04-16 14:04:16 +0200 |
|---|---|---|
| committer | Jeremy Allison <jra@samba.org> | 2019-08-08 20:24:32 +0000 |
| commit | 0b1d9d40c249ca7f893cbcc54587ae8fc93f15ee (patch) | |
| tree | 06cc15a35eb402e3934839a06b60bcc3d5664d0d /librpc | |
| parent | c742ab7a4c78db4101499d15ada1a6635d5cc35b (diff) | |
| download | samba-0b1d9d40c249ca7f893cbcc54587ae8fc93f15ee.tar.gz | |
s3:mdssvc: supposed status field is in fact a fragment indicator
Spotted this in mdssvc response that containied many results for a search
request: if the mdssvc response blob is larger then ~32k, the server fragments
the response in 32k fragments and sets the "fragment" field to 1.
Note that mdssvc implemenets result set "fragmentation" at the result set layer,
not at the marshalled response buffer layer. Therefor mdssvc always sets this
field to 0.
Signed-off-by: Ralph Boehme <slow@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>
Diffstat (limited to 'librpc')
| -rw-r--r-- | librpc/idl/mdssvc.idl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/librpc/idl/mdssvc.idl b/librpc/idl/mdssvc.idl index bfb27c4a795..43447961b0d 100644 --- a/librpc/idl/mdssvc.idl +++ b/librpc/idl/mdssvc.idl @@ -51,7 +51,7 @@ interface mdssvc [in] uint32 max_fragment_size2, [in] uint32 unkn7, /* always 0 ? */ [in] uint32 unkn8, /* always 0 ? */ - [out,ref] uint32 *status, + [out,ref] uint32 *fragment, [out,ref] mdssvc_blob *response_blob, [out,ref] uint32 *unkn9 /* always 0 ? */ ); |