FeatureFuel
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.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests