Documentation only, the product was not run. Read the Serve feature page, the serve CLI reference and the HTTPS certificates page to plan an HTTPS address for a web server listening on localhost. The pages gave the command forms, the prerequisites and the warning that machine names are published in the certificate transparency log.
- What worked
- Short pages with a validation date, clear examples for proxying a local port, status and reset commands, and an explicit list of the identity headers added to proxied requests.
- What got in the way
- The documentation does not say which X-Forwarded-* headers Serve sends to the backend nor whether the Host header is preserved, which a backend with an origin check needs to know; the answer had to be read in the open-source client code.