zlacker

[parent] [thread] 3 comments
1. adql+(OP)[view] [source] 2023-08-02 16:37:32
Right but then working slow looks like archive.is issue but is ultimately caused by cloudflare.

CF is bascically saying "we can know your IP but not the site you are trying to resolve" (that will know your IP anyway once you navigate there).

replies(2): >>yellow+dx >>jrochk+IQa
◧
2. yellow+dx[view] [source] 2023-08-02 18:53:37
>>adql+(OP)
> Right but then working slow looks like archive.is issue but is ultimately caused by cloudflare.

Whereas not loading at all looks like archive.is issue but is ultimately caused by archive.is.

> CF is bascically saying "we can know your IP but not the site you are trying to resolve" (that will know your IP anyway once you navigate there).

Not necessarily. For example, the DNS query could go straight to CF while the eventual request to archive.is goes through a proxy or VPN.

replies(1): >>sXgC6d+aO1
◧◩
3. sXgC6d+aO1[view] [source] [discussion] 2023-08-03 01:26:13
>>yellow+dx
Ok, really? Who is using a proxy for HTTP but not DNS in 2023?
◧
4. jrochk+IQa[view] [source] 2023-08-05 18:24:53
>>adql+(OP)
The current situation seems to be that for these users it's not working at all (either timeout or infinite captch loop), and it looks like an archive.is issue, no explanation is given. So avoiding service disruption looking like an archive.is issue does not seem to be the goal.
[go to top]