ladybird/Services/RequestServer/Cache
Timothy Flynn 20cd19be4d RequestServer: Store HTTP response headers in the cache index
We currently store response headers in the cache entry file, before the
response body. When we implement cache revalidation, we will need to
update the stored response headers with whatever headers are received
in a 304 response. It's not unlikely that those headers will have a size
that differs from the stored headers. We would then have to rewrite the
entire response body after the new headers.

Instead of dealing with those inefficiencies, let's instead store the
response headers in the cache index. This will allow us to update the
headers with a simple SQL query.
2025-11-02 13:03:29 -05:00
..
CacheEntry.cpp RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00
CacheEntry.h RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00
CacheIndex.cpp RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00
CacheIndex.h RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00
DiskCache.cpp RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00
DiskCache.h RequestServer: De-duplicate some disk cache requests 2025-10-28 11:52:51 +01:00
Utilities.cpp RequestServer: Create disk cache writers for new requests immediately 2025-10-28 11:52:51 +01:00
Utilities.h RequestServer: Create disk cache writers for new requests immediately 2025-10-28 11:52:51 +01:00
Version.h RequestServer: Store HTTP response headers in the cache index 2025-11-02 13:03:29 -05:00