Skip to content

Feature: CA-specific HTTP proxy settings #412

@mkauf

Description

@mkauf

A customer wants to use two different ACME CAs: one for internal domains (intranet), one for external domains (public websites). The ACME CA for the external domains is only reachable via an HTTP proxy. The HTTP proxy can only connect to the external ACME CA (not to the internal ACME CA).

Currently, it's not possible to configure mod_md for this scenario.

Possible solutions:

  • Allow the MDHttpProxy setting to be set per MDomain
  • Add a setting to skip the HTTP proxy for some specific hosts (curl option CURLOPT_NOPROXY)

I think that the first approach is better and easier to configure.

What do you think about this? I can submit a PR if you like one of the solutions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions