Post #451016
2026-02-28 07:57 UTC
@hongminhee@hollo.social you can use HTTP 3xx redirects but that's not strictly necessary because you can use DNS A/AAAA/CNAME as well (and have the HTTP server respond to those names in conjunction with TLS SNI)
the idea is that multiple server names can be responded to by the same Fedify software instance. in nginx it's doable with the http.server.server_name directive. https://nginx.org/en/docs/http/server_names.html
SNI: https://datatracker.ietf.org/doc/html/rfc6066#section-3
does fedify expect to run behind a reverse proxy? if so, it can route requests.
Replies (1)
-
@hongminhee@hollo.social 2026-02-28 08:02
@trwnh Fedify does run well behind a reverse proxy, and it doesn't actually require a fixed base URL—it can derive the base URL from the incoming request. Ghost takes advantage of exactly this to implement virtual hosting on top of Fedify, so in principle the kind of per-actor custom domain you're describing should already be achievable without changes to Fedify itself.