Open kassiansun opened 6 months ago
Here it says "for security reasons", is this still valid nowadays? The code was introduced at 2015: https://github.com/parse-community/Parse-SDK-iOS-OSX/blob/master/Parse/Parse/Internal/Commands/CommandRunner/URLSession/Session/PFURLSession.m#L261
New Issue Checklist
Issue Description
Currently,
parse-server
will returnETag
header for/parse/*
requests, but the client is not caching it properlySteps to reproduce
/parse/config
returned ETag header, but the parse client is not sendingIf-None-Match
along with the further requests to/parse/config
Actual Outcome
Expected Outcome
The client should obey the standard HTTP caching semantics, and re-use local cache if the ETag is consistent with remote version: https://www.rfc-editor.org/rfc/rfc9111.html
Environment
Client
2.7
Server
5.6.0
Ubuntu 22.04
AWS
Database
MongoDB
5.0
AWS
Logs