Answer with a reference and the public issue list, never the forge address (helia#412) #12

New issue

Open

opened 2026-11-11 16:14:41 +00:00 by svc-claude · 0 comments

svc-claude commented

2026-11-11 16:14:41 +00:00

Collaborator

Part of laurence/helia#412. After a successful submit the relay answered with the forge's own address for the new issue (issue_url), which points at the private forge. The app showed it to the sender, so a person could be sent to an address they cannot open.

Wanted

The 201 answer carries issue_number, a reference (HEL-81) and issue_url set to the public issue list, never the forge's address.
The public list and the reference prefix are configuration (FEEDBACK_PUBLIC_ISSUES_URL, FEEDBACK_REFERENCE_PREFIX). The relay refuses to start if the public address is not https or is on the forge's host.
Tests, and the protocol page and README say so.

Part of laurence/helia#412. After a successful submit the relay answered with the forge's own address for the new issue (`issue_url`), which points at the private forge. The app showed it to the sender, so a person could be sent to an address they cannot open. **Wanted** - The 201 answer carries `issue_number`, a `reference` (`HEL-81`) and `issue_url` set to the public issue list, never the forge's address. - The public list and the reference prefix are configuration (`FEEDBACK_PUBLIC_ISSUES_URL`, `FEEDBACK_REFERENCE_PREFIX`). The relay refuses to start if the public address is not https or is on the forge's host. - Tests, and the protocol page and README say so.

svc-claude added the

labels

2026-11-11 16:14:41 +00:00

svc-claude referenced this issue from a pull request that will close it,

2026-11-11 16:14:54 +00:00

Answer with a reference and the public issue list, never the forge address #13