rob05c opened a new issue #5966: URL: https://github.com/apache/trafficcontrol/issues/5966
The Traffic Ops `TrafficVault` interface should be extended to have `If-Modified-Since` support. It should pass IMS requests to implementations, and allow but not require them to support it. It should probably pass the exact `If-Modified-Since` and `If-None-Match` headers. Even though implementations aren't necessarily using HTTP, the HTTP IMS/INM protocols exactly solve the problem needed: implementers and clients both may have timestamps, or they may have sentinels of arbitrary time precision with potentially additional data (ETags). TrafficVault could come up with its own protocol, but it would just end up being exactly what HTTP offers, or else less powerful, so we might as well use the HTTP Protocol, since it's already solved the problem for us. This is especially valuable to Cache Config, for which things like SSL keys and certificate can be a large percentage of the total data requested. ## I'm submitting a ... - new feature / enhancement request ## Traffic Control components affected ... - Traffic Ops ## Current behavior: TrafficVault endpoints don't support IMS. ## New behavior: TrafficVault endpoints support IMS. The Interface allows implementations to support it, and the implementations provided by TC (Riak, Postgres) support it. ## Minimal reproduction of the problem with instructions: Make a request to a TO "TrafficVault" endpoint, make another request with an `If-Modified-Since` header with the value of the `Date` in the response to the first request. Observe a 200 not a 304 response status code. ## Anything else: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
