1e3b64c6c23f0bfe961007fac42c1992a5ac40a4
The previous commit's explanation of retargetUrls was inverted, in the message and in the comment. It said /user and /repos build from ROOT_URL and /contents from the public host. It is the other way round: this instance's app.ini has ROOT_URL = https://gitea.pastilhas.dev/, which is what /contents stamps, while /user and /repos echo the REQUEST host — loopback, because Officer dials http://localhost:9004 directly instead of going through the reverse proxy. Behaviour is unchanged and was already right: rewrite only a private/loopback URL, only onto a public target. Which half of the response is wrong does not affect that rule, which is why the bug did not show up in testing. But a comment that names the wrong cause is how the next change re-breaks it, so this corrects the record. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Description
No description provided
42 MiB
Languages
TypeScript
90.9%
Shell
4.7%
JavaScript
4.1%
CSS
0.2%
HTML
0.1%