SoupCache should also cached the sniffed content type
@carlosgc
Submitted by Carlos Garcia Campos Assigned to libsoup-maint@gnome.bugs
Link to original bug (#720877)
Description
When a resource doesn't have a Content-Type header, the sniffed content type is not available when the resource is loaded from the cache, because the sniffed content type is not cached. This caused problems in the WebKit resources mime type unit tests, see https://bugs.webkit.org/show_bug.cgi?id=126119. I think the disk cache should behave the same way that the memory cache, and in webkit, the memory cache saves the whole ResourceReponse, so that for a 304 response you still have a mime type in the response even if the Content-Type header is not present.
Version: 2.45.x