curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: can persistent auth be disabled?

From: Whitney Jackson via curl-library <>
Date: Fri, 28 Feb 2020 15:17:06 -0700

> This begs the question: how is curl supposed to figure this out rather
than to presume?

This seems to be the spec that covers that:

Summarizing, it looks like the correct behavior should be: queue requests
until you know whether you're doing persistent auth (aka connection based)
or non-persistent auth (aka request based). Switch to persistent auth only
if you get a response header that explicitly turns it on.

Seems like this part of curl needs some significant work. I'm thinking
about trying to do that myself. Would a contribution that attempts to make
curl's behavior line up with this specification be likely to be accepted?
Any thoughts or advice on how best to approach a contribution in this area
of the code? For example, is there a particular person who would want to
approve/disapprove a proposed design?


Received on 2020-02-28