Posts

Post marked as Apple Recommended
0 Views
The solution in my case was to create a new additional scheme only for authentication purpose e.g. "myappauth" Yes, that is the solution but in all cases its not possible to re-register scheme as we are accessing lot of customer portals. Would be grateful if someone from Apple address this. Regards, Nimesh
Post not yet marked as solved
2 Replies
0 Views
No, I haven't found any solution for this and logged a feedback with Apple.
Post not yet marked as solved
2 Replies
0 Views
Hi Matt,Sorry, but I'm not in control of the server to try changing anything server side.You can see in screenshots of the headers for request 1 and 2 - https://github.com/njarecha/URLCacheBug/blob/master/README.md, there are two additional headers `if-none-match` and `if-modified-since` for reqeust 2 which seems to be added based on cachePolicy by URLSession before sending request. The server is just honoring the provided headers and respond with status code `304`. So the question is why these headers are added to reqeust even though second request's HTTPbody is different than first request?Regards,Nimesh
Post not yet marked as solved
5 Replies
0 Views
Thank you for the response. I really apprciate it! It is going to be a big change in our codebase and we'll try to do that in near future but is there any workaround at this time to overcome 30 seconds delay?Regards,Nimesh
Post not yet marked as solved
5 Replies
0 Views
Thanks for the response!> Is there a specific reason you need these challenges?We have our own complex APIs with objects like Credential and Authentication Challenge. As you can see in the code the `performDefaultHandling` happens on the first challenge and it fails with an error. We notifiy the user/dev that they require to provide the credential to make it working. When user/dev provides credential/certificate, we send another request. At this time we expect the authentication challenge to be issued so we can pass on the credential/certificate. However, that does not happen due to this 30 second connection issue.Is there a work around or fix to overcome this 30 second connection issue?Regards,Nimesh