-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cf-ipfs.com
, cloudflare-ipfs.com
, and r2.dev
#1582
Conversation
4f1f3fb
to
c3192bc
Compare
Hi, @dnsguru. Is there an issue with this PR or can it be merged at some point soon? |
Had meant to do this and the r2 at same time but #volunteer got distracted by the stuff that pays for groceries and rent an all that today. @mathew-cf can you see if the r2 PR didn't create a re-base conflict on this? |
@mathew-cf @Frederik-Baetens please see if you can mash together #1582 and #1635 in one edit within this PR please so they don't "cross streams" in the bad, ghost-busters way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cf-ipfs.com
cf-ipfs.com
, cloudflare-ipfs.com
, and r2.dev
c3192bc
to
d9475f1
Compare
Soooo close... sort the entries by TLD then SLD (hint: TryCloudflare.com moves up above the .dev domains) |
I've updated the verification record for r2.dev to point to this PR instead:
|
e9f8b2d
to
f84da62
Compare
Should be ready to go now :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- DNS Validates
- Followed Guidelines
- No conflict w base
- Tests pass
APPROVED
Public Suffix List (PSL) Pull Request (PR) Template
Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowlegements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.
Checklist of required steps
Description of Organization
Reason for PSL Inclusion
DNS verification via dig
Run Syntax Checker (make test)
Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section
Submitter affirms the following:
For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
Description of Organization
Organization Website:
Organization Website: https://www.cloudflare.com/
Cloudflare is an edge network offering a variety of services, often serving as a reverse proxy and firewall. There is an existing email alias to be contacted over (publicsuffixlist@cloudflare.com).
Cloudflare provides CDN and DDOS protection, but we've recently launched R2, an object storage platform. This storage platform allows users to easily store arbitrary disorganized data for their applications.
I am an engineer working on web3 (including the IPFS Gateway) at Cloudflare. r2.dev is being added on behalf of @Frederik-Baetens who is an engineer on the R2 team.
Reason for PSL Inclusion
We're adding our IPFS gateways cloudflare-ipfs.com and cf-ipfs.com so that content served from the IPFS network is isolated per subdomain and to reduce the negative effects to the reputation of the domain.
Number of users this request is being made to serve:
Estimate of ~20k users/day based on Cloudflare's visit analytics.
Cloudflare R2 customers can make their buckets publicly available on r2.dev. When doing so, the customer gets a unique r2.dev subdomain associated with their specific bucket. These domains should be treated as separate domains for cookie purposes. Since these domains will often be used to serve files, things like "Sorting in the download manager" for Firefox will also be a nice added benefit.
Example of such a public url: https://pub-ae08589711b94eb3a7bf08c8750ccf2b.r2.dev/dog.jpg
Number of users this request is being made to serve: This would concern R2 customers, and all of their users, which is a large amount. The exact amount of customers is something I cannot disclose. If that's a problem, I can see if I can get permission to publish an approximate number.
DNS Verification via dig
Results of Syntax Checker (
make test
)All 5 tests passed