-
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 PSL Sandbox #2358
base: main
Are you sure you want to change the base?
add PSL Sandbox #2358
Conversation
I've considered doing something like this but adding testing entries to the production PSL should at least have clear goals. What exactly would we be testing and how? |
My goal for these entries would be to test cookie setting across through a web interface. With the results from these tests we could also make the wiki more specific on how cookied are affected. Also, it would allow people to test the effects of the PSL without having to add a staging domain to the list. |
We ended up shooting #1349 behind the woodshed. I think the premise of allowing cookie testing for a requestor is good. IF we set something like this up as the project, I suggest we should probably do so under publicsuffix.org domain vs one any of us individually are operating. |
Having it under publicsuffix.org would be good. Obviously I don't have access to the domain, so I just configured it on one of mine. Would we be able to configure some entries on publicsuffix.org? |
Let's discuss what we would hope to see accomplished in such a test, and then determine if the juice to squeeze is worth it on dealing with Mozilla's IT kafka pain to get records set up. |
The goal for this section of the PSL is to create a sandbox for testing the affects of different rules on the PSL.
This implements #1349.
The sandbox hasn't been deployed yet, however once these entries are listed I will deploy one so users can test out various differences domains have for when they are on the PSL.
Note: I have added these under subdomains of psl.hrsn.dev in order to prevent any potential problems or overlaps with the existence of the
hrsn.dev
rule. Also, I've added this in a new section as I would like these entries to remain as a separate "project" to Harrison Network specifically.It also might be worth noting that these will be the first exception rules
!
in the private section.All
_psl
TXT records have been put in place for the corresponding names.