replay web/ used to work perfectly. We could stream/show dynamically WACZ files on Drupal 9. But changes in Symfony? and also NGINX being more strict about this and of course a bit of our own (my own many mistakes) and the fact that Reply requests a HEAD but sends a range made suddenly all fail.
I found the culprit. On a HEAD request with a RANGE we return a partial 206 code, which for strict NGINX means: partial? remove the content-length, which also of course means replay not being able to read how much data is there an add dying
RFC says: return either 200 or a 204. We want to return a 200. We ignore Range now if the request is for a HEAD.
DiegoPino
commented
3 months ago
What?
replay web/ used to work perfectly. We could stream/show dynamically WACZ files on Drupal 9. But changes in Symfony? and also NGINX being more strict about this and of course a bit of our own (my own many mistakes) and the fact that Reply requests a HEAD but sends a range made suddenly all fail.
I found the culprit. On a HEAD request with a RANGE we return a partial 206 code, which for strict NGINX means: partial? remove the content-length, which also of course means replay not being able to read how much data is there an add dying
RFC says: return either 200 or a 204. We want to return a 200. We ignore Range now if the request is for a HEAD.
Pull coming.