"Same-site" and "same-origin" | Articles | web.dev

"Same-site" and "same-origin" Stay organized with collections Save and categorize content based on your preferences. "Same-site" and "same-origin" are frequently cited but often misunderstood terms. For example, they're used in the context of page transitions, fetch() requests, cookies, opening popups, embedded resources, and iframes. This page explains what they are and how they're different from

[efcl]

Cross-Origin-Resource-Policyなどの出てくる`site-site`と`site-origin`の違いについての解説。 same originはスキーマやportまで見る。 same siteはeTLD+1での一致をベースとしている

[Shisama]

日本語に翻訳されてる。ありがたや

[barlog]

“"Origin" is a combination of a scheme (also known as the protocol, for example HTTP or HTTPS), hostname, and port (if specified). For example, given a URL of https://www.example.com:443/foo , the "origin" is https://www.example.com:443”

[daido1976]

originとsiteの違い、めっちゃ分かりやすくて助かります。eTLDってなんだろうと思ってたけど、effective top-level domainの略なんですね。

[miya-jan]

same-origin と same-site の違いについて

[tofu-kun]

非常にわかりやすい解説。