-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
PublicSuffix list looks to be quite outdated and missing recent additions #7699
Comments
We should re-run okhttp/okhttp/src/jvmTest/java/okhttp3/internal/publicsuffix/PublicSuffixListGenerator.java Line 16 in 50a71e7
And get it into a 4.11. |
You can run it weekly on CI and have it make a PR if it has changed. Here's an example to copy: https://github.com/mdogan/homebrew-zulu/blob/master/.github/workflows/upgrade.yml |
Or since it only currently matters at the point of cutting a release, generating an updated suffix list at point of release maybe? Would it be possible to get an idea on:
Even if you currently have no estimate to offer, knowing even that would still be useful for me to make some decisions around this. Ta! |
@swankjesse does the releases, but I don't think he'll want to give an exact date. My guess is small number of weeks rather than months. |
The ideal release process is a tag on an existing, tested SHA. Changing data at release prevents adequate testing. |
Sorry for the bump, but wondering if there's likely to be any movement on this soon? |
Hey 👋
I'm looking here https://github.com/square/okhttp/tree/master/okhttp/src/jvmMain/resources/okhttp3/internal/publicsuffix and seeing the public suffix list hasn't been updated in 2 years.
I ask because I noticed
foo.myshopify.com
andbar.myshopify.com
are both returningmyshopfiy.com
as e-TLD+1, despitemyshopify.com
being on the public suffix list.Questions
okhttp
to provide a newer public suffix list forokhttp
to consume?Thanks!
The text was updated successfully, but these errors were encountered: