-
Notifications
You must be signed in to change notification settings - Fork 6
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
Possible issue with gzip compressed responses #9
Comments
The workaround is to set |
xhr is still not perfect, it is good that you found solution. use Line 56 in 5a40d48
https://github.com/ewsjs/xhr/blob/5a40d48be49bf0b7a57e9bca128d7cc4824f99b3/src/xhrApi.ts#L277-L228 |
Yes this also works (and is possibly a better workaround) |
I will also activate this setting for |
The
request
library does not handle compression by default.Here is what happens when I try to use NTLM with xhr:
The response is not parsed correctly:
I believe the problem is related to request/request#539 of the new
request
library used by xhr (fetch
was not affected by this).The problem seems to be fixed by adding
gzip: true
in the request options, although I am not sure this covers 100% of cases.The text was updated successfully, but these errors were encountered: