You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a server (or proxy) returns a Content-Type header together with a 304 response (indicating that the cached resource is still valid and does not need reloading), the browser uses this instead of the cached mime type.
Because of this issue in the WebOne proxy, this is actually a relevant problem.
I will fix this on the 149-host-tcpip-socket-driver branch.
The text was updated successfully, but these errors were encountered:
When a server (or proxy) returns a
Content-Type
header together with a 304 response (indicating that the cached resource is still valid and does not need reloading), the browser uses this instead of the cached mime type.Because of this issue in the WebOne proxy, this is actually a relevant problem.
I will fix this on the
149-host-tcpip-socket-driver
branch.The text was updated successfully, but these errors were encountered: