.well-known struggles and a work around

[bhyde (Ben)]

I found it challenging to serve up the .well-known files as part of a matrix messaging installation. Matrix is described here: Introduction | Matrix.org. These servers are federated and they discover each other using either SRV records in DNS or with well known files, for example: https://matrix.org/.well-known/matrix/server.

It took me a while to realize that the redir directive is such high priority. Like many sites I redir all traffic from to www..

I ended up with this caddy configuration for :

http://<DOMAIN>.org {
        redir https://www.<DOMAIN>.org{uri}
}

https://<DOMAIN>.org {
    route {
        reverse_proxy /.well-known/matrix/* https://matrix.<DOMAIN>.org {
            header_up Host matrix.<DOMAIN>.org
        }
        redir https://www.<DOMAIN>.org{uri}
    }
}

I failed to puzzle out how to do this with the simplified config file.

Maybe this will be helpful for others.

But, I’m curious if my solution can be improved?

[francislavoie]

Yeah, you pretty much have the simplest way to do it.

This article should answer some of your remaining questions:

Composing in the Caddyfile

Web server config files are mostly about expressing HTTP handling logic. Often, various handlers or middlewares need to be “composed” to form a cohesive HTTP handler that returns the desired responses. Structurally, config files are basically limited to two dimensions: rows and columns (or, lines and tokens). Syntactically, a config file’s second dimension can expand into more dimensions or scopes when blocks are opened (which are usually represented by curly braces { } and/or indentation, simi…

[bhyde (Ben)]

It’s funny how every easy to use DSL ends up with an appendix in the doc ike that. Been there!