mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-10-19 07:33:20 +00:00
9b8f6b8108
If transferring a cached response body fails for any reason, we will now issue a network request instead of failing the request outright. The catch here is that we will have already transferred the response code and headers to the client, and potentially some of the body. So we attempt to only request the remaining data over the network using a range request. This feels a bit sketchy, but this is also how Chromium behaves. However, the server may or may not support range requests. If they do, we can expect an HTTP 206 response with the bytes we need. If not, we will receive an HTTP 200 (assuming the request succeeded), along with the entire object's body. In this case, we also behave like Chromium, and internally drop number of bytes we had already transferred. |
||
|---|---|---|
| .. | ||
| ImageDecoder | ||
| RequestServer | ||
| WebContent | ||
| WebDriver | ||
| WebWorker | ||
| CMakeLists.txt | ||