Skip to content

Support digest authentication for HTTP proxies. #2033

Closed

Description

@lovelydinosaur

Escalating discussion #2028 into an issue.

HTTP proxies are sometimes configured to use digest authentication.
Right now we only support basic authentication with HTTP proxies.
It'd be worthwhile to also support digest - which requires following up the initial CONNECT request to the proxy with a subsequent authentication request before the proxy tunnel is established.

Here's the original discussion...

Originally posted by raffaem January 13, 2022
Does httpx support DigestAuthentication for proxies, and if so, can you connect to HTTPS websites through a proxy that requires DigestAuthentication?

requests-toolbet has a HTTPProxyDigestAuth class, but it does not allow you to connect to HTTPS through the proxy.

Apparently that feature won't be implemented in the foreseeable future in requests.

The only working implementation that I have found, and which allows you to connect to HTTPS websites through the proxy, is this one, which was provided in this StackOverflow post.

Does httpx support this feature, or will it support it?

Activity

  1. stale commented on Feb 20, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  2. lovelydinosaur commented on Feb 21, 2022

    @lovelydinosaur
    MemberAuthor

    Still valid thx, @Stale bot.

  3. stale commented on Mar 25, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  4. stale commented on Oct 15, 2022

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  5. lovelydinosaur commented on Jul 31, 2023

    @lovelydinosaur
    MemberAuthor

    I think we should consider closing this since we've only had one person ever request this.

    There's enough documentation and pointers around httpcore for someone who's interested to be able to start tackling it. If someone ends up interested and invested in resolving that, then I think that'd be a good indicator that it'd be worth re-opening.

    Seem valid @encode/maintainers?

  6. lovelydinosaur commented on Sep 6, 2023

    @lovelydinosaur
    MemberAuthor

    I'm going to close this ticket off for now - if someone bumps into this as a requirement please let us know.
    Otherwise / until then, we'll be treating this as out of scope.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestproxiesIssues related to HTTP and SOCKS proxieswontfix

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions