Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
toot.community is one of the many independent Mastodon servers you can use to participate in the fediverse.
A worldwide Mastodon instance from The Netherlands. Run by digital enthusiasts, inviting everyone, everywhere to join us in the #fediverse.

Administered by:

Server stats:

2.1K
active users

toot.community: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#IdentityCrisis

2 posts2 participants0 posts today
Public
N-gated Hacker News

Oh, the drama! 🕵️‍♂️ Chrome's epic identity crisis: returning 206 instead of 403, just to make your #debugging experience a gift 🎁 that keeps on giving. Clearly, #WASM is the real MVP here for disappearing #bugs faster than Houdini. 🐛✨
aoli.al/blogs/chrome-bug/ #Chrome #Drama #IdentityCrisis #HackerNews #ngated

aoli.alChrome Returns 206 when the Server Returns 403 – Ao LiPostmortem It is a feature not a bug! I got detailed explanation from chrome developers which is very helpful. You may find the complete response in the bug ticket. Also this blog post draws a lot of attention after I post it on Hackers News. You may find comments here. Updates: I did know the people who replied my issue are not the developers as pointed out by a HN comment. I was also pretty surprised when the OP said “the Chromium team refused to use my server to reproduce the bug”, when the actual comments of the ticket were “clone this repo and run my giant node app” and the tester’s response was “It seems a bit difficult to set up an build environment to run the static server, could you provide a more minimal repro case?”. OP’s description of the tester’s reasonable concerns seems very unfair. |Ao Li
ExploreLive feeds
About