Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @silverpill@mitra.social
marius@mariusor@metalhead.club (2026-05-16 17:43:41)
@silverpill to come back to this, I have added both this example and one of your original requests to the unit-tests, and they both validate correctly.

So I still have no idea why this is failing in production. The only thing I can think of is the http proxy messing with the value of the "target-uri" parameter.
---Reply---
silverpill@silverpill@mitra.social (2026-05-17 06:37:09)
@mariusor That's possible.

@target-uri is supposed to be an absolute URI. HTTP servers typically re-construct full URI using the Host and other headers. For example, I use this method: https://docs.rs/actix-web/latest/actix_web/dev/struct.ConnectionInfo.html#method.host

Hostname is resolved through the following, in order:
Forwarded header
X-Forwarded-Host header
Host header
request target / URI
configured server hostname

If I don't configure my reverse proxy to set these headers, the full URI will be incorrect, leading to verification failure.