Caddyfile adapter wraps localhost into automation policy for public names

[mholt]

This minimal Caddyfile:

{
	email foo@bar
}

localhost {
}

example.com {
}

yields automation policies in JSON:

[
  {
    "subjects": [
      "example.com",
      "localhost"
    ],
    "issuers": [
      {
        "email": "foo@bar",
        "module": "acme"
      },
      {
        "email": "foo@bar",
        "module": "zerossl"
      }
    ]
  }
]

which is clearly wrong, because localhost can't get a cert from Let's Encrypt or ZeroSSL (or any publicly-trusted CA).

Already have a fix incoming. Just making this issue for future reference.

(Edit: Looks like we have a test that is actually enforcing this behavior, global_options_preferred_chains.txt - but there's no way that's intentional, right?)

[francislavoie]

Yeah - that test is incorrect. 👍