Server sometimes responds with HTTP 200 even when If-None-Match matches ETag

Chiming in to say that I’m seeing the behaviour as described in this topic, so I assume that this hasn’t been fixed, two years later. I understand the need to prioritise, but this should be fixed.