2
Compress text API responses before leaving data centre
Source: supabase/supabase#13769 · opened by @DevOfManyThings
Feature request Is your feature request related to a problem? Please describe. Currently Supabase compresses text payloads at the CDN (confirmed in email with support): This means the egress data sent from Supabase's servers which manage the pooled connections to the database send out the raw payloads uncompressed, which uses significantly more data than if compression were to be moved to those servers rather than handled by the CDN. Describe the solution you'd like Supabase to move the point of compression to the servers which expose the REST API for text base responses. This compression should reflect in the egress data usage. As the data is already being sent to the client compressed, this change could be handled by Supabase transparently without requiring updates by end users, and cause a significant drop in their egress data bill. Describe alternatives you've considered N/A Additional context This won't help applications w…
No pledges yet. Be the first to back this.
Comments
Similar requests
Support Content-Encoding header for upload routes
2 votes · 0 comments
Compression Issue with ‘application/vnd.pgrst.object+json’ Content-Type in PostgREST Responses
3 votes · 0 comments
Authenticated API Endpoint to Restart / Toggle Database On & Off Remotely
2 votes · 0 comments
Request for Improved Response Status in supabase.auth
7 votes · 0 comments
Feture Request: Want to get some part of data encrypted via RSA Private keys to avoid client side data manipulation
1 vote · 0 comments
No comments yet.