dearsky/numa
1
0
Fork 0
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 25 Wiki Activity

docs(config): fix ODoH relay path in numa.toml example #139

Merged
razvandimescu merged 1 commits from fix/odoh-relay-doc-path into main 2026-04-23 13:58:53 +08:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
razvandimescu commented 2026-04-23 13:53:51 +08:00 (Migrated from github.com)
Copy Link

Summary

  • numa.toml line 46 advertised the ODoH relay at https://odoh-relay.numa.rs/proxy, but the live server only serves /relay (returns 404 on /proxy, 405 on GET /relay as expected for an ODoH POST endpoint).
  • Every other reference in the tree already uses /relay — src/config.rs rustdoc + tests, packaging/client/numa.toml — so this was an isolated typo introduced in 2e461cc ("docs(config): add ODoH upstream examples…"), shipped in 0.14.2.
  • One-line fix. Users who copied the example verbatim saw UPSTREAM ERROR | ODoH relay returned 404 Not Found → SERVFAIL on every query.

Reported by @bcookatpcsd in #138. Their workaround (swapping in odoh-relay.edgecompute.app) confirmed the relay choice wasn't at fault — only the path.

Test plan

  • curl -I https://odoh-relay.numa.rs/relay → 405 (method not allowed on GET, correct)
  • curl -I https://odoh-relay.numa.rs/proxy → 404
## Summary - `numa.toml` line 46 advertised the ODoH relay at `https://odoh-relay.numa.rs/proxy`, but the live server only serves `/relay` (returns 404 on `/proxy`, 405 on `GET /relay` as expected for an ODoH POST endpoint). - Every other reference in the tree already uses `/relay` — `src/config.rs` rustdoc + tests, `packaging/client/numa.toml` — so this was an isolated typo introduced in 2e461cc ("docs(config): add ODoH upstream examples…"), shipped in 0.14.2. - One-line fix. Users who copied the example verbatim saw `UPSTREAM ERROR | ODoH relay returned 404 Not Found` → SERVFAIL on every query. Reported by @bcookatpcsd in #138. Their workaround (swapping in `odoh-relay.edgecompute.app`) confirmed the relay choice wasn't at fault — only the path. ## Test plan - [x] `curl -I https://odoh-relay.numa.rs/relay` → 405 (method not allowed on GET, correct) - [x] `curl -I https://odoh-relay.numa.rs/proxy` → 404
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 docker
Pull requests that update docker code
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 rust
Pull requests that update rust code
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dearsky
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/numa#139
Delete Branch "fix/odoh-relay-doc-path"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?