-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache control not applied when uploading files #550
Comments
Hi @florian-mlr thansk for the report. Regarding cache control, I was able to reproduce it, I'm checking with backend, the lib seems to be correctly sending the request. About |
Hey @grdsdev , thank you for the quick reply How do you log headers ?
Yes it breaks the logic in my app, the error is thrown when i make this call |
Hello @grdsdev |
In the meantime i've created my own function :
|
Hi @florian-mlr can you confirm you get I'm still doing a few tests and wasn't able to get |
Hello @grdsdev ! When checking on the browser, i get On your side, does my code work too ? |
@florian-mlr when I download the file uploaded by your code, I still get |
I'm downloading the image with AsyncImage in iOS and with Coil in Android by giving the public url. I'm not using the library to download image. |
Bug report
Describe the bug
I have noticed an issue regarding the "Cache-Control" header. After uploading an image and explicitly specifying the "cacheControl" option, I find that when I subsequently retrieve the image, the header does not include the intended "Cache-Control" configuration. Instead, it appears that the cache control is set to "no-cache."
To Reproduce
Upload an image and set the cache control
When fetching the uploaded image, the header contains "Cache-Control: no-cache"
Expected behavior
When fetching the uploaded image, the header should contains "Cache-Control: max-age=172800"
System information
Additional context
I also want to mention that I tried updating the library to v2.20.0 to check if the issue is resolved. However, when I proceeded with the update, I encountered an error: "error: errSecItemNotFound: The item cannot be found." Due to this error, I decided to abandon the migration.
The text was updated successfully, but these errors were encountered: