Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FSSHTTPWOPIInspector: sub responses are not fully read #83

Open
germany1234 opened this issue Apr 4, 2024 · 3 comments
Open

FSSHTTPWOPIInspector: sub responses are not fully read #83

germany1234 opened this issue Apr 4, 2024 · 3 comments

Comments

@germany1234
Copy link

i monitored some fsshttp traffic with fiddler and inspected the result.
if subresponses are read, e.g. the query access response, the parsing stops in the middle of the payload.
according to the documentation it is parsed in the correct way, but I see the following.
there is the 16 bit object stream header end that is parsed at the end. the header type is incorrect (the correct header end type is at the real end of the payload), which is not detected by the parser.
all following data is simply ignored by the plugin.
which means, the documentation (the MS-FSSHTTPB document) has some issues here or there is some hidden information. Since I'm interested in that protocol and in the fiddler inspector, I would like to have a fix. the official document seems to be wrong. may be there is a way to get more information. I attached an example fsshttpb response which is parsed successfully but not in total and the final 16 bit object stream header end is never reached. the extension is dmp, it is a binary file
example.dmp

@germany1234
Copy link
Author

issue.zip
here the fiddler trace
and here some effect, the header type is wrong (329), which the parser does not detect and simply ignores everything what follows.
inspector

@xian-rong
Copy link
Contributor

@germany1234 we are working on the troubleshooting to resolve this issue.

@xhong812
Copy link

@germany1234 , we are investigating, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants