| 3 Jun 2025 |
edef | iirc we don't have a flag for accurately selecting them | 19:44:06 |
edef | * iirc we don't have a flag for accurately selecting them by | 19:44:32 |
Arian | yeh so all the user agents are Nix in the top-most amount of requests | 19:47:40 |
Arian | So I feel like we might have a nix bug that makes some request use HTTP 1.1 for whatever reason or really a lot of people are behind weird corpo proxies | 19:48:11 |
hexa | also Lix from AS8881 is Versatel | 19:49:28 |
hexa | which is an eyeball network | 19:49:31 |
hexa | * also Lix from AS8881 (Versatel 1&1) | 19:49:41 |
Arian | oh the top result is actually no user agent | 19:50:54 |
hexa | so if anything something before nix 2.19 and nothing newer | 19:50:57 |
hexa | Redacted or Malformed Event | 19:51:37 |
hexa | pennaes first suspicion is that h1 would be used if the h2 connection setup failed | 19:52:21 |
hexa | there is no explicit fallback, so either users explicitly configuring it or a curl thing | 19:53:23 |
Arian | so the no-user-agent requests from Amazon are only requesting narinfo files it seems | 19:57:31 |
Arian | so I guess some scraper | 19:59:59 |
Arian | other theory: some Fastly PoPs fail to negotiate HTTP 2.0 for some reason | 20:07:23 |