Skip to content
This repository was archived by the owner on Mar 10, 2026. It is now read-only.
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

Closed

Description

@ElariefN

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

Activity

  1. michaelrsweet commented on Jul 27, 2016

    @michaelrsweet
    Contributor

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

  2. added this to the Future milestone on Jul 27, 2016
  3. michaelrsweet commented on Aug 24, 2016

    @michaelrsweet
    Contributor

    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.

  4. modified the milestones: Future, on Jun 29, 2017
  5. 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
  6. michaelrsweet commented on Nov 6, 2017

    @michaelrsweet
    Contributor

    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)

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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions