Regex for matcher

[psyciknz]

Trying to get a specific regex for a general matcher…but I want it to exclude some certain strings, eg hass or unifi.
My initial base is:
(.*)\.mydom.com

This finds everything. To exclude unifi.mydom.com and hass.mydom.com I managed to get the following to work in regex101.com

 ^((?!hass|unifi).*)\.mydom.com

But I’m trying to feed this to caddy, and it’s complaining it’s not valid perl (I’d have thought it was go). regex for go doesn’t see to have a negative lookahead.

What I’m wanting is in a Caddyfile to deal with a reverse proxy matcher, and only if not found to use the (.*).mydom.com at the end.

internal.mydom.com:443 {
        @unifi host unifi.mydom.com
        reverse_proxy @unifi 192.168.10.41:8444 {
            transport http {
                tls_insecure_skip_verify
            }
        }

    @allSubdomains header_regexp sub host (.*)\.mydom.com
    handle @allSubdomains {

       reverse_proxy {re.sub.1}.drogo.mydom.com:443
    }
}

What seems to happen with this, is if I put unifi.mydom.com it still gets to the @allSubDomains.

[francislavoie]

Next time, please fill out the help topic template, as per the forum rules. It’s important so we get full context for your question, to make sure we’re on the same page. Because of that, I need to make some assumptions, which may be incorrect.

@psyciknz

But I’m trying to feed this to caddy, and it’s complaining it’s not valid perl (I’d have thought it was go). regex for go doesn’t see to have a negative lookahead.

I don’t understand. Please show the error message you got. Caddy definitely uses Go’s regexp engine, RE2: Syntax · google/re2 Wiki · GitHub

If all you need is to grab the part of a domain, you can use {labels.*} placeholders, i.e. {labels.2} for the subdomain (where the number is right-indexed, so 0 is com).

@psyciknz

What I’m wanting is in a Caddyfile to deal with a reverse proxy matcher, and only if not found to use the (.*).mydom.com at the end.

The reason that Caddyfile doesn’t work is because directives are sorted according to a predetermined order (see Caddyfile Directives — Caddy Documentation), where handle is higher than reverse_proxy, so your regexp one runs first. You can run caddy adapt --pretty --config /path/to/Caddyfile to see the JSON output which will show you exactly the order directives were sorted.

Please also see the reverse_proxy docs about proxying to HTTPS upstreams:

reverse_proxy (Caddyfile directive) - Caddy Documentation

[psyciknz]

Sorry, there was exception, I suspect related to go/perl (whatever caddy uses) not supporting a negative lookahead, can ignore this thread.

I’m still struggling with my concept of using caddy-docker-proxy which creates the c addy file dynamically, and dns. I just can’t get my head over having to put in entries for each service in dns and then have all the reverseproxy entries created automatically.

I have another thread I need to raise regarding env variables (for cloudflare key) not being loaded. So will fill in template for that.