> That's also basically what the CA caching does.
The caching does a bit more - it stores the parsed bundle. > If you ask me, that's almost like begging for problems since you then ditch > the caches and ruins the ability to do things faster in subsequent transfers, > over and over. Agree 100%. Unfortunately, I'm not the author of this code, and we have to be extremely careful when changing anything. Like recently I finally managed to fix the code to properly use all the parameters to produce desired request, instead of abusing CURLOPT_CUSTOM_REQUEST. Of course immediately someone complained, that the POST now sends chunked encoding and the server (Microsoft SSO) does not understand it at all.... > Sure that's possible, but is the difference between that and the blob approach > you already mentioned adding anything extra? Yep, this basically re-invents the caching of the parsed bundle. -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcurl.se%2Fsupport.html&data=05%7C01%7C%7Ccea5294de8dc4af837ac08db3f42aba3%7C9a21e1abb7a74f828fd0170bb7e09f92%7C0%7C0%7C638173327799232688%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=15F6nr126Y%2F1RrDz6swpC5YnS5VzKzieNyvZKZUxB18%3D&reserved=0<https://curl.se/support.html>
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
