3
Compression Issue with ‘application/vnd.pgrst.object+json’ Content-Type in PostgREST Responses
Source: supabase/supabase#28757 · opened by @istarkov
I've noticed an issue with the PostgREST library (postgrest-js) when using the [.single()]( query. The library correctly sets the Accept header to application/vnd.pgrst.object+json (as per the [PostgREST documentation]( and the server responds with the same content-type header. However, it seems this content-type is not being treated as compressible on your server, unlike other content-types. _It's important to note that this issue only occurs with .single() calls. All other queries are being compressed without any issues._ This might be due to the absence of 'application/vnd.pgrst.object+json' in your API proxy configuration, such as in nginx_proxy_brotli_types ([Kong documentation]( or a similar proxy you use. To reproduce the issue: 1. Run PostgREST on your database with the Accept header set to 'application/vnd.pgrst.object+json'. 2. Observe that the content is not compressed, and check the amount of data received (you can use Chrome DevT…
No pledges yet. Be the first to back this.
Comments
Similar requests
Custom query parameter on postgrest-js
4 votes · 0 comments
Allow configuring PostgREST pool and pooler in Supabase CLI (api.db_pool, api.use_pooler)
1 vote · 0 comments
Introducing supabase to the Haskell ecosystem
9 votes · 0 comments
Compress text API responses before leaving data centre
2 votes · 0 comments
Support nulls=stripped introduced by PostgREST 11.2.0
2 votes · 0 comments
No comments yet.