| 19 Sep 2025 |
 @ghpzin:envs.net | Yes, that was for previous issue when there was js error and nothing loaded.
Not sure if current issue is related to security fix that was the reason for that.
It is weird, because on other prefixes there is only 1 request and it is fine, on those there is first one and then the always spamming one.
Both return 200 with what seems to be correct things: <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>...
I guess pagination does not work, first request on spamming ones returns:
<MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>true</IsTruncated>
Working ones return <MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated> | 19:10:51 |
| @ghpzin:envs.net | Yes, that was for previous issue when there was js error and nothing loaded.
Not sure if current issue is related to security fix that was the reason for that.
It is weird, because on other prefixes there is only 1 request and it is fine, on those there is first one and then the always spamming one.
Both return 200 with what seems to be correct things: <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>...
I guess pagination does not work, first request on spamming ones returns:
<IsTruncated>true</IsTruncated>
Working ones return <IsTruncated>false</IsTruncated> | 19:11:19 |
 vcunat | I think those pages did work at some point, but I haven't tried very recently to be sure that they did break right now around those security fixes. | 19:14:24 |
| vcunat | * I believe those pages did work at some point, but I haven't tried very recently to be sure that they did break right now around those security fixes. | 19:14:32 |
