My endpoints provide an If-None-Match header when making requests to the API, according to the requirements set out here: https://grahamrpugh.com/2024/07/22/sofa-new-feed.html. They are using cURL's --etag-compare and --etag-save features.
When the server responds with 304: Not Modified, the ETag is unexpectedly missing from the response header, see here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/304.
Because of the failure to include the ETag in the response header, cURL overwrites the local ETag cache with a null value. On the next check-in, clients will provide a blank If-None-Match header and force the server to re-send all the data.
My endpoints provide an
If-None-Matchheader when making requests to the API, according to the requirements set out here: https://grahamrpugh.com/2024/07/22/sofa-new-feed.html. They are using cURL's--etag-compareand--etag-savefeatures.When the server responds with 304: Not Modified, the ETag is unexpectedly missing from the response header, see here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/304.
Because of the failure to include the ETag in the response header, cURL overwrites the local ETag cache with a null value. On the next check-in, clients will provide a blank If-None-Match header and force the server to re-send all the data.