Colton Idle
03/19/2024, 8:18 PMETag
and Last-Modified:
but it seems like the follow up request uses ETAG in the response. Whereas my server team really wants us to use Last-Modified.yschimke
03/19/2024, 10:03 PMyschimke
03/19/2024, 10:04 PMyschimke
03/19/2024, 10:06 PMjessewilson
03/20/2024, 12:58 AMglureau
03/20/2024, 8:28 AMyschimke
03/20/2024, 8:28 AMjessewilson
03/20/2024, 11:00 AMyschimke
03/20/2024, 11:38 AMColton Idle
03/20/2024, 1:36 PMyschimke
03/20/2024, 1:51 PMColton Idle
03/20/2024, 5:27 PMHTTP/1.1 200 OK
Date: Wed, 20 Mar 2024 17:25:11 GMT
Server: Apache/2.4.41 (Ubuntu)
X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Last-Modified: 2023-09-12T15:48:48.000Z
Content-Type: application/json; charset=utf-8
Content-Length: 455
ETag: FOO
Keep-Alive: timeout=5, max=99
Connection: Keep-Alive
and here is the subsequent request
GET /api/blah
HTTP/1.1
Authorize: BLAH
Host: <http://blah.com|blah.com>
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent: okhttp/4.11.0
If-None-Match: FOO
yschimke
03/20/2024, 6:50 PMColton Idle
03/20/2024, 8:10 PMjessewilson
03/21/2024, 1:58 AMjessewilson
03/21/2024, 2:00 AM