MapService Layers/Features and 304 responses

[Anonymous User]

Original User: jmurdoch

Under what circumstances will a request to a layer, layer query, or a particular feature return a 304 response? 

For example, if I change a particular attribute value on a single feature, I might expect the next request to that feature _not_ to yield a 304.  (Is this so?)  However, what if that attribute is a coded domain value in which the code remains constant, but the defined name for the code has changed (seen at the layer level)?

[RaviNarayanan]

If the request header included a IF-NONE-MATCH=<etag> header and if the ETAG matches for the response, then server will return a 304-NOT MODIFIED status for the response.

There is a bug where the feature resource is cached and might return a 304-NOT MODIFIED even when one of the attribute values for the feature has changed. QUERY will return the correct response with the updated feature.

If the description of a layer changes then you need to refresh the service and clear REST cache for the changes to be reflected in the layer resource.