Content-Range for INSERTs and UPDATEs

[sted]

It appears that PostgREST sends a Content-Range: */* header for POST requests, regardless of the Prefer: return setting.

However, for PATCH requests, it sends a Content-Range header that indicates the number of records updated (e.g., Content-Range: 0-2/*), again irrespective of the Prefer: return setting.

What is the rationale behind this behavior?

[sted]

To add context, I verified this behaviour on version 12.0.2, without using the Range header in the requests, which is now ignored for POST and PATCH methods.

I would add an issue about this, but I think this will be resolved when the Shortcomings in HTTP compliance #1089 are corrected:

PostgREST uses the Range and Content-Range headers defined in RFC 7233, but it doesn’t implement RFC 7233 properly. Firstly, PostgREST sends Content-Range on all kinds of responses, including 200 (OK) to GET, 201 (Created) to POST, and 204 (No Content) to DELETE. But in RFC 7233 Content-Range is only a feature of special partial responses, which are indicated by status code 206 (Partial Content), which in turn can’t happen unless the request has a Range.

I am writing some comments about pagination, count and Range headers in Pagination and Count for SmoothDB.