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
I have searched the tracker for existing similar issues and I know that duplicates will be closed
Describe the Issue
The Postman client does not follow up with the second request in Digest Auth scenarios, when the server responds with "digest ......" keyword in header, instead of "Digest .......".
This makes the client remain in the Unauthorized state for each request that comes back with the "digest ..." header set.
The keyword was changed to "Digest" using a Proxy and Postman behaved as usual.
Steps To Reproduce
Open new request tab
Select Digest auth
Add username and password
Call the API service
If the response header is set as "digest ...." the second request does not follow
Screenshots or Videos
Operating System
macOS
Postman Version
10.24.3
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
No response
The content you are editing has changed. Please copy your edits and refresh the page.
@paulcristiann,Thank you for reporting this. I can replicate the issue. As per RFC-6617, both the scheme and parameters should be handled in a case-insensitive manner. We are tracking this as a bug and will provide updates on the same thread.
Is there an existing issue for this?
Describe the Issue
The Postman client does not follow up with the second request in Digest Auth scenarios, when the server responds with "digest ......" keyword in header, instead of "Digest .......".
This makes the client remain in the Unauthorized state for each request that comes back with the "digest ..." header set.
The keyword was changed to "Digest" using a Proxy and Postman behaved as usual.
Steps To Reproduce
Screenshots or Videos
Operating System
macOS
Postman Version
10.24.3
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
No response
Tasks
The text was updated successfully, but these errors were encountered: