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
It seems that either the storage API is ignoring the if-modified-since header or the Cloudflare cache is ignoring it, as I seem to always get the file even though it has not been modified.
I was unable to find out what version of the storage API is running on my hosted instance, so I couldn't add that information. If you can tell me where to find this information, I can include it.
The text was updated successfully, but these errors were encountered:
I believe that the PR you linked only provided the solution for the S3 backend. Maybe the free/hosted version of Supabase does not use this backend and the used backend does not support this functionality.
The only thing I can say for certain is that the problem still exists.
Bug report
Describe the bug
It seems that either the storage API is ignoring the if-modified-since header or the Cloudflare cache is ignoring it, as I seem to always get the file even though it has not been modified.
To Reproduce
("-I" to show document info only)
Expected behavior
The file should not be returned as it has not been modified and the http-status-code should be 304.
Actual
The file is returned and the status-code is 200.
Additional context
I was unable to find out what version of the storage API is running on my hosted instance, so I couldn't add that information. If you can tell me where to find this information, I can include it.
The text was updated successfully, but these errors were encountered: