on 2023 May 01 9:45 AM
Hi all,
We seem to have a problem with sending multiple delete requests to the Microsoft graph api where we get timeouts on subsequent outlook deletion of meeting requests.
SAP suggests that this could be because the MS graph api does not support (or handle well) subsequent requests over the same http connection.
They say and I quote:
According to RFC specification of HTTP 1.1 protocol, if the server is not explicitly providing Connection:close header in the response, it means that it should be able to handle subsequent requests within the same connection. It is not the case here.
So i was wondering if there is a way to force CPI to make a new connection in a subsequent message, or failing that to force close the connection when the call has been made.
Thanks!
Tom
Request clarification before answering.
User | Count |
---|---|
63 | |
8 | |
7 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.