We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/public-folder-access-with-ews-in-exchange#routing-public-folder-requests, setting the X-PublicFolderMailbox HTTP header is necessary in some circumstances.
X-PublicFolderMailbox
The logic in deciding when to set it and what to put as the value is described in the link, and the routing possibilities are detailed in https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-route-public-folder-hierarchy-requests and https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-route-public-folder-content-requests
Spoiler: it's non-trivial.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
According to https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/public-folder-access-with-ews-in-exchange#routing-public-folder-requests, setting the
X-PublicFolderMailbox
HTTP header is necessary in some circumstances.The logic in deciding when to set it and what to put as the value is described in the link, and the routing possibilities are detailed in https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-route-public-folder-hierarchy-requests and https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-route-public-folder-content-requests
Spoiler: it's non-trivial.
The text was updated successfully, but these errors were encountered: