You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like #2272 took a bit of a nuclear approach to solving this problem, which prevents me from continuing to reuse the session. It must reauthenticate each time if I'm talking to the same realm.
On subsequent requests the Authentication header is missing forcing a reauthentication. I don't expect this if I'm only using a single curl object for a single realm. Technically the reauthentication doesn't prevent the request from going through, but it certainly is less efficient requiring an extra handshake for each request.
I verified my app works perfectly when not reseting the digest info. The nc increments perfectly with each request and it never gets any additional 401s after the initial authentication.
The first time I expect the server to return 401 with WWW-Authenticate header.
The CURL adds digest info to Authorization header and resends.
The second time I reuse the curl I expect the Authorization header to be sent with nc=00000002.
curl/libcurl version
7.62.0
operating system
Windows 7
The text was updated successfully, but these errors were encountered:
Related:
#2255
#2347
Related PR
#2272
It looks like #2272 took a bit of a nuclear approach to solving this problem, which prevents me from continuing to reuse the session. It must reauthenticate each time if I'm talking to the same realm.
On subsequent requests the Authentication header is missing forcing a reauthentication. I don't expect this if I'm only using a single curl object for a single realm. Technically the reauthentication doesn't prevent the request from going through, but it certainly is less efficient requiring an extra handshake for each request.
The offending line is here.
curl/lib/easy.c
Line 1024 in 2f5f31b
I verified my app works perfectly when not reseting the digest info. The nc increments perfectly with each request and it never gets any additional 401s after the initial authentication.
I did this
suppose url and userpswd don't change.
I expected the following
This should only authenticate once.
The first time I expect the server to return 401 with WWW-Authenticate header.
The CURL adds digest info to Authorization header and resends.
The second time I reuse the curl I expect the Authorization header to be sent with nc=00000002.
curl/libcurl version
7.62.0
operating system
Windows 7
The text was updated successfully, but these errors were encountered: