We are not emitting Cache-Control field when responding producing a response, but we are required to do so.

Furthermore we are faking ETag header based on schema, which is entirely incorrect, as it does not reflect the content of the datastore.

We are also producing Last-Modified header indicating the resource was modified at the time the request has completed in a format not compatible with HTTP.

Finally, we are producing these headers only for GET request on /data, but not in POST or PUT.

Correct this by:

1. always emitting Cache-Control: no-cache
2. delegating the responsibility for ETag/Last-Modified to a particular RestconfStrategy

As part of this change we will not generate these headers, but define the APIs so that individual strategies can provide them, subject to subsequent improvements.