Remove asuracomic.net: pin the userscript, CORS allowlist, fixtures and notes to asurascans.com #96

New Issue

2026-08-12T00:35:30+07:00

sulthan commented

2026-08-12 00:35:30 +07:00

Follow-up to #94, deliberately separate: the registry pin now rejects stored
asuracomic.net addresses cleanly, but the rest of the stack still names the
dead domain, and a CORS or deploy mistake around it must not be confusable
with a registry bug.

Why

asuracomic.net deep links 301 to the asurascans.com root, discarding the
path (re-checked 2026-07-25). A stored series_url on that host previously
fetched the asura homepage and parsed the wrong document. After #94 it fails
cleanly instead — this issue removes the remaining references.

Files

backend/.env.example:18 and docker-compose.yml:28 — ALLOWED_ORIGINS
drops https://asuracomic.net.
DEPLOY.md:46 — same allowlist.
userscript/manga-bookmark.user.js:9 (@match) and :120 (host regex
/(^|\.)asurascans\.com$|(^|\.)asuracomic\.net$/).
backend/api_test.go:36,172,180 (CORS fixtures reflecting
https://asuracomic.net) and :207-211 (seed data on the old host).
README:3, README:277-281, root AGENTS.md:9.
Live .env on the VPS (deploy step, after this lands).

One-off repair (confirm against one real row first)

UPDATE series SET series_url = replace(series_url, '//asuracomic.net/', '//asurascans.com/')
WHERE series_url LIKE 'https://asuracomic.net/%';

Build hash in those rows will be stale, but asura 302s stale hashes to the
current build (sites_test.go:184-185) and the TLS fetcher follows redirects.

Follow-up to #94, deliberately separate: the registry pin now rejects stored asuracomic.net addresses cleanly, but the rest of the stack still names the dead domain, and a CORS or deploy mistake around it must not be confusable with a registry bug. ### Why asuracomic.net deep links 301 to the asurascans.com **root**, discarding the path (re-checked 2026-07-25). A stored `series_url` on that host previously fetched the asura homepage and parsed the wrong document. After #94 it fails cleanly instead — this issue removes the remaining references. ### Files - `backend/.env.example:18` and `docker-compose.yml:28` — `ALLOWED_ORIGINS` drops `https://asuracomic.net`. - `DEPLOY.md:46` — same allowlist. - `userscript/manga-bookmark.user.js:9` (`@match`) and `:120` (host regex `/(^|\.)asurascans\.com$|(^|\.)asuracomic\.net$/`). - `backend/api_test.go:36,172,180` (CORS fixtures reflecting `https://asuracomic.net`) and `:207-211` (seed data on the old host). - README:3, README:277-281, root `AGENTS.md:9`. - Live `.env` on the VPS (deploy step, after this lands). ### One-off repair (confirm against one real row first) ```sql UPDATE series SET series_url = replace(series_url, '//asuracomic.net/', '//asurascans.com/') WHERE series_url LIKE 'https://asuracomic.net/%'; ``` Build hash in those rows will be stale, but asura 302s stale hashes to the current build (sites_test.go:184-185) and the TLS fetcher follows redirects.

sulthan referenced this issue from a commit

2026-08-12 05:49:45 +07:00

chore: drop asuracomic.net from the userscript, CORS allowlist and docs (#96)

sulthan referenced this issue from a commit

2026-08-12 05:49:45 +07:00

chore: refresh code graph (#96)

sulthan referenced a pull request that will close this issue

2026-08-12 05:50:10 +07:00

chore: drop asuracomic.net from the userscript, CORS allowlist and docs #97

sulthan closed this issue

2026-08-12 05:53:19 +07:00

sulthan referenced this issue from a commit