Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

NullReferenceException in WrapStream when ContentEncoding is null #217

Open
OriginalPerson opened this issue Dec 14, 2018 · 3 comments · May be fixed by #248
Open

NullReferenceException in WrapStream when ContentEncoding is null #217

OriginalPerson opened this issue Dec 14, 2018 · 3 comments · May be fixed by #248

Comments

@OriginalPerson
Copy link

OriginalPerson commented Dec 14, 2018 •
edited
Loading

When server return InternalServerError WrapStream method throws NullReferenceException. It`s throws because ContentEncoding is null.
image
image
image
@jschoombee
Copy link

finding the same issue if no content-encoding in http response it is not handled.

AlbertoMonteiro added a commit to AlbertoMonteiro/ews-managed-api that referenced this issue Apr 8, 2020
@AlbertoMonteiro
Handling empty content-encoding header
9db26c4 
Fixes OfficeDev#217
AlbertoMonteiro added a commit to AlbertoMonteiro/ews-managed-api that referenced this issue Apr 8, 2020
@AlbertoMonteiro
Handling empty Content-Encoding header
676fecc 
Fixes OfficeDev#217
@AlbertoMonteiro AlbertoMonteiro linked a pull request Apr 8, 2020 that will close this issue
Open
@Annosz Annosz mentioned this issue May 11, 2020
Merged
@ntziolis
Copy link

ntziolis commented May 21, 2021 •
edited
Loading

Same here Exchange 2016. O365 works fine.

@ntziolis ntziolis mentioned this issue May 21, 2021
Open
@dseph
Copy link

dseph commented Dec 9, 2021

I ran into someone with this issue. It was resolved by setting the X-AnchorMailbox header to the destination mailbox.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handling empty Content-Encoding header AlbertoMonteiro/ews-managed-api
4 participants
@ntziolis @dseph @jschoombee @OriginalPerson