| 3 Jun 2025 |
 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 |
| hexa | uh, we only use the shield pop | 20:07:38 |
| hexa | https://github.com/NixOS/infra/issues/212#issuecomment-1187503882 is a great post that explains the setup | 20:08:10 |
| hexa | I don't think much has changed since it was potsed | 20:08:18 |
| hexa | * I don't think much has changed since it was posted | 20:08:25 |
 edef | note that S3 only speaks HTTP/1.1 | 20:14:13 |
| edef | are you sure you are measuring client requests to the CDN and not origin requests? | 20:14:36 |
| edef | because curling narinfos definitely gives me h2 | 20:15:18 |
| edef | and like, we might just be logging this wrong, this data may not exist, i am not sure | 20:19:18 |
| Arian | yeh im pretty sure these are client requests to the cdn | 20:19:38 |
| edef | the logs are literally some json we sprintf together | 20:19:46 |
| edef | * the logs are literally some "json" we sprintf together | 20:19:52 |
| Arian | ah | 20:19:54 |
