Token list page not resolving ENS address

[Rachel-Eichenberger]

I verified json schema
can import on uniswap UI, but fails to load on tokenlists.org
tokenlist.tkr.eth
https://bafybeiasb3nnwwaigkqrhs4z7ac2ygulgeb3v352fahhdwqkf7mpntkgty.ipfs.dweb.link/

[doplur]

See a slightly updated version at: list.tkn.eth or https://list.tkn.eth.limo/

[doplur]

It appears that there's a CORS issue with the Uniswap cloudflare worker that's serving ENS data:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wispy-bird-88a7.uniswap.workers.dev/?url=http://list.tkn.eth.link. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 409.

[Rachel-Eichenberger]

It appears that there's a CORS issue with the Uniswap cloudflare worker that's serving ENS data:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://wispy-bird-88a7.uniswap.workers.dev/?url=http://list.tkn.eth.link. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 409.

@doplur
So I didn't realize this in haste this morning...
This block would be on your end, You might need a dedicated point for your IPFS list.

but if you look other lists with ENS are loading like 1 inch. I will have to close this

[doplur]

So after parsing down a bit, it would appear that the problem stems from Cloudflare's .link resolver, which is used exclusively by the https://wispy-bird-88a7.uniswap.workers.dev/?url=http://list.tkn.eth.link worker.
By poking the SSL certificate generator in the ENS manager, I was able to get the .link resolver to recover from it's SSL error for this ENS URL. However, eth.link has been notoriously finicky over the last few months, so it may be best to provide multiple gateways with which to resolve ENS data.

[Rachel-Eichenberger]

Well I'll leave for the team to see, but check this out incase
I know I had to update my cors policy to stop errors
https://github.com/Uniswap/token-lists#authoring-token-lists