GITHUB . COM {
}
Detected CMS Systems:
- Wordpress (2 occurrences)
Title:
Cookie partitioning on localhost is underspecified · Issue #10867 · whatwg/html
Description:
What is the issue with the HTML Standard? This was originally opened as an issue on the CHIPS standard, but I was advised to open an issue here instead. My understanding is that normally, otherwise-identical URLs that have different port...
Website Age:
17 years and 8 months (reg. 2007-10-09).
Matching Content Categories {📚}
- Technology & Computing
- Dating & Relationships
- Social Networks
Content Management System {📝}
What CMS is github.com built with?
Github.com is based on WORDPRESS.
Traffic Estimate {📈}
What is the average monthly size of github.com audience?
🚀🌠 Tremendous Traffic: 10M - 20M visitors per month
Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.
check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush
How Does Github.com Make Money? {💸}
Subscription Packages {💳}
We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.How Much Does Github.com Make? {💰}
Subscription Packages {💳}
Prices on github.com are in US Dollars ($).
They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.
Wordpress Themes and Plugins {🎨}
What WordPress theme does this site use?
It is strange but we were not able to detect any theme on the page.
What WordPress plugins does this website use?
It is strange but we were not able to detect any plugins on the page.
Keywords {🔍}
issue, cookie, localhost, sign, cookies, open, partitioning, domains, domain, partitioned, navigation, html, pull, requests, actions, security, underspecified, opened, standard, port, treated, set, attribute, share, topic, github, type, projects, milestone, footer, skip, content, menu, product, solutions, resources, source, enterprise, pricing, search, jump, whatwg, public, notifications, fork, star, code, issues, wiki, insights,
Topics {✒️}
assigned labels topic comment metadata assignees personally find chrome' receiving cookies open partitioned cookies html standard originally opened cookie type partitioning chips standard identical urls port numbers server running port number spec directly type projects projects milestone milestone relationships domain attribute github cookie localhost domains localhost domains issue chrome domains domain partitioned localhost sign skip jump advised understanding treated default purpose setting set received firefox means shared equivalent share behaviour preferable firefox' addressed
Payment Methods {📊}
- Braintree
Questions {❓}
- Already have an account?
- What is the issue with the HTML Standard?
- While I personally find Chrome's behaviour here preferable to Firefox's, could this issue be addressed in the spec directly, so that there isn't two different behaviours here?
Schema {🗺️}
DiscussionForumPosting:
context:https://schema.org
headline:Cookie partitioning on localhost is underspecified
articleBody:### What is the issue with the HTML Standard?
This was originally opened as an issue [on the CHIPS standard](https://github.com/privacycg/CHIPS/issues/92), but I was advised to open an issue here instead.
My understanding is that normally, otherwise-identical URLs that have different port numbers are treated as different domains... except on localhost, where they are treated as the same domain by default. (For the purpose of setting and receiving cookies).
So if a cookie is set for localhost:1142, it will also be received by a server running at localhost:1141, even if it doesn't set the Domain attribute.
In Chrome, this happens even if the cookie is partitioned. In Firefox, however, [the partitioning uses the port number](https://bugzilla.mozilla.org/show_bug.cgi?id=1925171#c7), which means that partitioned cookies cannot be shared between localhost domains. Even though the equivalent non-localhost domains could share the same partitioned cookies using the Domain attribute.
While I personally find Chrome's behaviour here preferable to Firefox's, could this issue be addressed in the spec directly, so that there isn't two different behaviours here?
author:
url:https://github.com/Sora2455
type:Person
name:Sora2455
datePublished:2024-12-17T02:17:17.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:0
url:https://github.com/10867/html/issues/10867
context:https://schema.org
headline:Cookie partitioning on localhost is underspecified
articleBody:### What is the issue with the HTML Standard?
This was originally opened as an issue [on the CHIPS standard](https://github.com/privacycg/CHIPS/issues/92), but I was advised to open an issue here instead.
My understanding is that normally, otherwise-identical URLs that have different port numbers are treated as different domains... except on localhost, where they are treated as the same domain by default. (For the purpose of setting and receiving cookies).
So if a cookie is set for localhost:1142, it will also be received by a server running at localhost:1141, even if it doesn't set the Domain attribute.
In Chrome, this happens even if the cookie is partitioned. In Firefox, however, [the partitioning uses the port number](https://bugzilla.mozilla.org/show_bug.cgi?id=1925171#c7), which means that partitioned cookies cannot be shared between localhost domains. Even though the equivalent non-localhost domains could share the same partitioned cookies using the Domain attribute.
While I personally find Chrome's behaviour here preferable to Firefox's, could this issue be addressed in the spec directly, so that there isn't two different behaviours here?
author:
url:https://github.com/Sora2455
type:Person
name:Sora2455
datePublished:2024-12-17T02:17:17.000Z
interactionStatistic:
type:InteractionCounter
interactionType:https://schema.org/CommentAction
userInteractionCount:0
url:https://github.com/10867/html/issues/10867
Person:
url:https://github.com/Sora2455
name:Sora2455
url:https://github.com/Sora2455
name:Sora2455
InteractionCounter:
interactionType:https://schema.org/CommentAction
userInteractionCount:0
interactionType:https://schema.org/CommentAction
userInteractionCount:0
External Links {🔗}(3)
Analytics and Tracking {📊}
- Site Verification - Google
Libraries {📚}
- Clipboard.js
- D3.js
- Lodash
Emails and Hosting {✉️}
Mail Servers:
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
Name Servers:
- dns1.p08.nsone.net
- dns2.p08.nsone.net
- dns3.p08.nsone.net
- dns4.p08.nsone.net
- ns-1283.awsdns-32.org
- ns-1707.awsdns-21.co.uk
- ns-421.awsdns-52.com
- ns-520.awsdns-01.net