You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One might expect that the header for the initial request is applied to all pages of the iterator.
What do you think? Is the current behavior expected, or is this something that could be improved? It could either copy headers from the "TCollectionPage" to each page request. Or it could also raise an exception if the "TCollectionPage" contains headers instead of providing them to the iterator itself, as it probably has unexpected results if using it this way.
The text was updated successfully, but these errors were encountered:
You can create a request that fetches a calendar item content as plain text like this:
You could put this response object in an iterator:
But there, the "Prefer" header is only applied to the first page, the rest of the calendar items returns the html body.
Solution/Workaround: set the header in the iterator instead:
One might expect that the header for the initial request is applied to all pages of the iterator.
What do you think? Is the current behavior expected, or is this something that could be improved? It could either copy headers from the "TCollectionPage" to each page request. Or it could also raise an exception if the "TCollectionPage" contains headers instead of providing them to the iterator itself, as it probably has unexpected results if using it this way.
The text was updated successfully, but these errors were encountered: