Daniel is worth following on the Fediverse if you have an account. He shares interesting stories from maintaining curl such as one where a user raised an issue with curl but it turned out that curl was correctly identifying that the users antivirus was acting as a MITM on their network: https://mastodon.social/@bagder/109880784239388087
Ah, I've been on that conversation a few times. My favorite has been a couple of times the conversation went some variant like this:
"Why can't I download this thing from you?"
You have a web filter that is forbidding you.
"No, I don't have a web filter."
Yes, you do.
"No, I definitely don't. You and/or your product suck if they can't download a simple file like this."
Here's the exact page & headers the download process is getting; you have $BRAND web filter, it is complaining that you're violating $POLICY, and it says it's located on this IP/domain address.
"Stop making excuses and just fix it."
Sir, if I was able to just reach out and disable your web filter, you would not actually be happy about that.
"I DON'T. HAVE. A. WEB. FILTER."
(Some hours pass)
"I have spoken with IT and it turns out we do have a web filter. A local blame-finding and finger-pointing meeting has been scheduled for who snuck that on to the network without telling anyone else in the organization. I have now redirected all my quite substantial and more-than-a-little profanity-laced anger towards my IT team, which as I am the VP of $DEPT is going to be a bad time for them; heads may roll. In the meantime, we've gotten the whitelist entry added for this and your stuff is now working fine."
---
I interpolate a little, obviously, and this is a composite of several incidents I've had over the years, but I do sometimes enjoy the little subtle hints dropped in the last communication we receive on the matter that mean that my last interpolation there is likely quite accurate.