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
{{ message }}
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
"algorithm" field is not supported in the WWW-Authenticate header of a 401 response #4862
When the printer responds with a 401 and states in the response header that it supports sha256 and md5, the response sent back does not contain the algorithm to be used and hence the printer uses md5. Is there a way to configure the use of sha256 when the printer supports it? We're using cupsDoIORequest to make the request with CUPS version 1.6.3. Thank you
The algorithm field is brand new in the latest HTTP Digest update and is not supported by any version of CUPS right now (and very little client software at all).
I'll use this bug to track adding support in a future release (but not 2.2...)
changed the title [-]"algorithm" field is not supplied in the header at a 401 response[/-][+]"algorithm" field is not supported in the WWW-Authenticate header of a 401 response[/+]on Nov 1, 2017
Activity
michaelrsweet commentedon Jul 27, 2016
The algorithm field is brand new in the latest HTTP Digest update and is not supported by any version of CUPS right now (and very little client software at all).
I'll use this bug to track adding support in a future release (but not 2.2...)
michaelrsweet commentedon Aug 24, 2016
We will also use this bug to track supporting multiple WWW-Authenticate header values so that we can choose among the supported ways to authenticate.
[-]"algorithm" field is not supplied in the header at a 401 response[/-][+]"algorithm" field is not supported in the WWW-Authenticate header of a 401 response[/+]Support the latest HTTP Digest authentication specification (Issue #4862
michaelrsweet commentedon Nov 6, 2017
Quite the substantial set of changes, but I think we've ended up in a happy place...
[master 2b4f6f21a] Support the latest HTTP Digest authentication specification (Issue #4862)
Backport CUPS 2.3.x changes to 2.2.x (Issue #5255)
Fix crash bug in HTTP field handling - regression in the backported c…