Skip to content
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

Closed
CDRussell opened this issue Feb 17, 2023 · 7 comments
Closed
Labels
bug Bug in existing code

Comments

@CDRussell
Copy link

CDRussell commented Feb 17, 2023

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 and bar.myshopify.com are both returning myshopfiy.com as e-TLD+1, despite myshopify.com being on the public suffix list.

Questions

  1. Is the file I linked to above just a placeholder, and an updated version is grabbed some other way, or is it really just quite outdated?
  2. Is there some mechanism I should be doing outside of okhttp to provide a newer public suffix list for okhttp to consume?

Thanks!

@CDRussell CDRussell added the bug Bug in existing code label Feb 17, 2023
@yschimke
Copy link
Collaborator

We should re-run

And get it into a 4.11.

@JakeWharton
Copy link
Collaborator

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

@CDRussell
Copy link
Author

CDRussell commented Feb 20, 2023

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:

  1. how likely this will be updated in the next release?
  2. when that next 4.11 release might be available (days/weeks away?)

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!

@yschimke
Copy link
Collaborator

5.x PR #7700
4.x PR #7701

@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.

@JakeWharton
Copy link
Collaborator

The ideal release process is a tag on an existing, tested SHA. Changing data at release prevents adequate testing.

@CDRussell
Copy link
Author

Sorry for the bump, but wondering if there's likely to be any movement on this soon?

@yschimke
Copy link
Collaborator

yschimke commented May 8, 2023

It's in 4.11

https://github.com/square/okhttp/blob/master/docs/changelogs/changelog_4x.md

@yschimke yschimke closed this as completed May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug in existing code
Projects
None yet
Development

No branches or pull requests

3 participants