Comment 4 for bug 1773463

I'm fine with supporting *.domain.com, just wanted to point out that Go
doesn't, by default, support it, though it does support .domain.com, etc.
(So the same limitations are part of lxd and probably snaps.)

John
=:->

On Thu, May 31, 2018 at 11:48 AM, Dmitrii Shcherbakov <
<email address hidden>> wrote:

> I'd say the wildcard syntax is more common as it is described in a
> relevant RFC: https://tools.ietf.org/html/rfc4592#section-2.1.3
> "
> A wildcard "blocks itself" in the sense that a wildcard does not match its
> own subdomains. That is, "*.example." does not match all names in the
> "example." zone; it fails to match the names
> below "*.example."
> "
>
> ~~
>
> no-proxy=.domain.com
> or no-proxy=*.domain.com
> or no-proxy=.domain.com.
> or no-proxy=*.domain.com.
>
> will match:
>
> domainhost1.domain.com
> domainhost1.domain.com.
> domainhost2.domain.com
> domainhost2.domain.com.
>
> but not
>
> subhost.subdomain.domain.com
> subhost.subdomain.domain.com.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1773463
>
> Title:
> [2.4-beta3] wildcard syntax is not supported by no-proxy/juju-no-proxy
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1773463/+subscriptions
>