Follow-up from #2122 (review by rzo1).
okhttp punycodes the host when it parses a URL: IDN.toASCII("ExAmpleé.org") gives xn--exampl-gva.org. URLUtil.getCanonicalHost (introduced in #2122 for politeness queues and the robots.txt cache) lowercases and percent-decodes the host but does not punycode it, so the Unicode and punycode spellings of one server still get separate politeness queues and separate robots.txt cache entries:
http://ExAmpleé.org/ → host ExAmpleé.org → key examplé.orghttp://xn--exampl-gva.org/ → key xn--exampl-gva.org
Suggested fix: apply IDN.toASCII in getCanonicalHost (falling back to the raw host when the label is not a valid IDN), so both spellings collapse the way okhttp collapses them at connect time.
Follow-up from #2122 (review by rzo1).
okhttp punycodes the host when it parses a URL:
IDN.toASCII("ExAmpleé.org")givesxn--exampl-gva.org.URLUtil.getCanonicalHost(introduced in #2122 for politeness queues and the robots.txt cache) lowercases and percent-decodes the host but does not punycode it, so the Unicode and punycode spellings of one server still get separate politeness queues and separate robots.txt cache entries:http://ExAmpleé.org/→ hostExAmpleé.org→ keyexamplé.orghttp://xn--exampl-gva.org/→ keyxn--exampl-gva.orgSuggested fix: apply
IDN.toASCIIingetCanonicalHost(falling back to the raw host when the label is not a valid IDN), so both spellings collapse the way okhttp collapses them at connect time.