Plain http:// bookmarks are rejected

Nobody has started this yet — be first.

Business impact

Anyone saving a plain http:// link -- an internal tool, an old blog, a local dev server -- gets a hard 400, even though the API's own documented contract ("url must use http or https") promises both are supported. This reads as a broken product for the (still common) case of non-https pages.

Problem

validateURL now rejects every scheme except https. The error message it returns still claims both are accepted, which is actively misleading.

Current behavior

POST /bookmarks with a http:// URL returns 400 "url must use http or https", even though http:// is exactly one of the two schemes that message says are accepted.

Expected behavior

Both http:// and https:// are accepted; every other rejection (empty URL, relative path, other schemes, no host) is unchanged.

Steps to reproduce

curl -s -X POST http://localhost:8081/bookmarks -H 'Content-Type: application/json'
-d '{"url":"http://intranet.local/wiki","title":"Internal wiki"}'

Expected: 201

Actual: 400 {"error":"url must use http or https"}

Why this matters

A two-branch scheme check lost one branch -- most plausibly a partial edit toward an https-only policy that never finished. It compiles and passes every existing test cleanly because none of them happen to POST an http:// URL.

Suggested approach

Compare the scheme check in validateURL against its own doc comment two lines above, which still describes accepting "http(s)".

Acceptance criteria

http://example.com/page → 201.
https://example.com/page → 201 (don't regress the happy path).
ftp://example.com → 400 (still rejected).
Empty/relative URLs still 400 -- must not break TestCreate_MalformedInputRejected.

Verification

go test ./practicetickets/... -run TestTicket03 -v

Hints (0/2)

Try it without hints first — the reading is the exercise.

Working on this ticket

Work on a branch named for the ticket — that's what you'll submit.

Branch off your fork

$git checkout -b fix/http-scheme-rejected

Fix it and commit

Meet every acceptance criterion, and add a test that would have caught this.

Push the branch

$git push -u origin fix/http-scheme-rejected

Submit it below

Paste your fork URL and the branch name, with a short write-up of the root cause.

Submit your fix

Questions

Stuck on something?

Ask about anything unclear in the ticket — the maintainer and anyone who has solved it can answer. Please don't post full solutions.

No questions yet. If something in this ticket reads ambiguously, you are probably not the only one — ask.

The project

Bookmark Manager — Parameterized Filtering Done Right

A small, real bookmark-saving API whose entire reason for existing is teaching the habit of building tag/search SQL filters with parameterized queries -- clause list and argument slice built in lockstep -- instead of string-concatenated SQL, even in an app "nobody" is attacking.

Fork on GitHub

Download

Setup

Bookmark Manager — Parameterized Filtering Done Right

git clone <your-fork>
cd go/bookmark_manager
cp .env.example .env   # optional, defaults already work
docker compose up --build   # postgres (host 5433) + app (host 8081)

The app waits for Postgres to become reachable, then applies (idempotent -- safe to rerun on every startup) before serving traffic.