The api-catalog document points at a dead repository URL for the mobile API docs #67

New issue

Open

opened 2026-11-03 18:52:34 +00:00 by skippy-bot · 0 comments

skippy-bot commented

2026-11-03 18:52:34 +00:00

Problem

The /.well-known/api-catalog document publishes a service-doc link for the mobile channel at https://github.com/gmcintire/aprs.me/blob/main/docs/mobile-api.md. That repository answers 404, so the machine-readable pointer that crawlers and clients follow leads nowhere, while the document itself is served from the live repo and from the app.

Evidence

At 2f150f66:

lib/aprsme_web/controllers/page_controller.ex:106 hard-codes the GitHub URL.
docs/mobile-api.md:540 names https://github.com/aprsme/aprs.me/issues as the project, which resolves.
curl -s -o /dev/null -w '%{http_code}' https://github.com/gmcintire/aprs.me answers 404 today, while https://github.com/aprsme/aprs.me answers 200.

Expected

The catalog advertises a URL that resolves to the current mobile API document.

How to verify

curl -s https://aprs.me/.well-known/api-catalog | jq -r '.linkset[1]["service-doc"][0].href', then request that URL and check the status code.

Acceptance criteria

Every service-doc href in the catalog resolves.
A test asserts the published links are absolute and point at the canonical repository.

Effort: S
Lens: api

## Problem The `/.well-known/api-catalog` document publishes a `service-doc` link for the mobile channel at `https://github.com/gmcintire/aprs.me/blob/main/docs/mobile-api.md`. That repository answers 404, so the machine-readable pointer that crawlers and clients follow leads nowhere, while the document itself is served from the live repo and from the app. ## Evidence At `2f150f66`: - `lib/aprsme_web/controllers/page_controller.ex:106` hard-codes the GitHub URL. - `docs/mobile-api.md:540` names `https://github.com/aprsme/aprs.me/issues` as the project, which resolves. - `curl -s -o /dev/null -w '%{http_code}' https://github.com/gmcintire/aprs.me` answers 404 today, while `https://github.com/aprsme/aprs.me` answers 200. ## Expected The catalog advertises a URL that resolves to the current mobile API document. ## How to verify `curl -s https://aprs.me/.well-known/api-catalog | jq -r '.linkset[1]["service-doc"][0].href'`, then request that URL and check the status code. ## Acceptance criteria - [ ] Every `service-doc` href in the catalog resolves. - [ ] A test asserts the published links are absolute and point at the canonical repository. **Effort:** S **Lens:** api

skippy-bot added the

Low

bug

effort: S

labels

2026-11-03 18:52:34 +00:00