1
Storage should return 404 in HTTP status code when object is not found
Source: supabase/supabase#42287 · opened by @l2dy
Storage should respond with status code 404 instead of 400 if object is not found. This was previously proposed in and it's clear that returning 400 is not semantically correct.
Returning 400 with a statusCode embedded in response body also makes it more difficult to differentiate different kind of failures without peaking into response body, which is more expensive for reverse proxies and middleware to implement.
Returning 400 with a statusCode embedded in response body also makes it more difficult to differentiate different kind of failures without peaking into response body, which is more expensive for reverse proxies and middleware to implement.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add "status" column in subscriptions stripe to where filter "status" works outside of attrs
2 votes · 0 comments
Return user metadata from Storage API "list" endpoint
1 vote · 0 comments
Add Storage Backups in Sync with Database Backups
4 votes · 0 comments
Add Storage Adapter For Chrome.Local.Storage Api
3 votes · 0 comments
# Proposal: Virtual Storage Columns (Seamless DB-to-Storage Mapping)
1 vote · 0 comments
No comments yet.