TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why Google prepend while(1); to their JSON responses

76 点作者 tymscar超过 2 年前

3 条评论

H4ZB7超过 2 年前
because the web is broken in every way imaginable for no reason and should have been discontinued about 14 years ago. but this is really old, now my favorite is dns rebinding [1]. this has to be one of the most beautiful examples of how core web devs do not understand ANYTHING. every single thing they have ever done is a misconception. not a single web dev related disclosure for the last 20 years has given me insight on how to design secure systems; it&#x27;s always just a thing that would not exist in any alternate design.<p>1. <a href="https:&#x2F;&#x2F;github.com&#x2F;mpgn&#x2F;ByP-SOP">https:&#x2F;&#x2F;github.com&#x2F;mpgn&#x2F;ByP-SOP</a>
评论 #34787713 未加载
评论 #34785198 未加载
评论 #34785226 未加载
评论 #34785607 未加载
Gigachad超过 2 年前
Interesting that the issue was solved in 2011 but presumably, the risk that someone is still using a 12+ year old browser is greater than the benefit of removing this trick. I wonder if they would ever deem it safe to remove.
评论 #34807611 未加载
Waterluvian超过 2 年前
So the protection was trapping the sinister script context running in my browser in an infinite loop. Clever!<p>…Does that grind my browser to a halt?<p>Why not just throw an error or something?
评论 #34784382 未加载
评论 #34785024 未加载
评论 #34784173 未加载