When running behind a reverse proxy, the path of the proxy may differ from that of the CherryPy application. For instance, CherryPy may think it's running on http://localhost:8187/, but the reverse proxy makes it available as https://example.com/biblemunger. In that scenario, URLs generated by CherryPy in HTTP redirects, or in HTML, will be localhost URLs, and the reverse proxy will have to rewrite the HTML and/or HTTP headers by parsing the content and doing a regex replace on the URLs - not ideal from a speed or security perspective.
Instead, you can use this tool to tell CherryPy to use a different base URL like so:
0 comments on commit
12c3348