Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Digest Auth not starting second request in certain scenarios #12727

Closed
1 task done
paulcristiann opened this issue Mar 19, 2024 · 2 comments
Closed
1 task done

Digest Auth not starting second request in certain scenarios #12727

paulcristiann opened this issue Mar 19, 2024 · 2 comments

Comments

@paulcristiann
Copy link

paulcristiann commented Mar 19, 2024

Is there an existing issue for this?

  • 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.

Screenshot 2024-03-19 at 17 42 13

Steps To Reproduce

  1. Open new request tab
  2. Select Digest auth
  3. Add username and password
  4. Call the API service
  5. 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

Tasks

No tasks being tracked yet.
@sandeep-singh-pstmn
Copy link

sandeep-singh-pstmn commented Mar 20, 2024

@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.

mdn web-docs - https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/WWW-Authenticate#directives

@sandeep-singh-pstmn
Copy link

@paulcristiann We have fixed this issue in the latest version of the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants