Repository navigation
Tags
Tags
Release v1.1.1: routing collisions and static site precedence Three routing defects with the same shape: a route was stored but could not be reached, and nothing said so. - Two backends sharing a hostname and a path prefix both registered, unwarned - AddBackend appended prefixed routes instead of updating them - roji config reload silently dropped a static site whose hostname a container had taken, until roji restarted A static site declared in the config file now keeps its hostname, which is what request handling and startup ordering already did.
Release v1.1.0: bind setting, loopback by default, routing and WebSoc… …ket fixes Breaking: roji listens on 127.0.0.1 and ::1 instead of every interface. Set `bind` to widen it again — see the Configuration guide for reaching roji from another device. Also: six routing and WebSocket defects found by review, WebSocket upgrades served through httputil.ReverseProxy (permessage-deflate now works end to end), and golangci-lint added to CI.
PreviousNext