GET
. This is exactly the same thing that web browsers do to revalidate some resources that they cache on the client. But here it is about Form Runner caching form definitions obtained from the persistence layer.GET
s with the Last-Modified
and If-Modified-Since
HTTP headers. However the built-in eXist and relational persistence layer implementations do not support these headers properly yet.ETag
and If-None-Match
, which will be required for persistence layers that support versioning.If-Modified-Since
HTTP header, for example:200
status code.304
("not modified") status code, without the need to send any response body.Last-Modified
header, for example:GET
method and, optionally, for the HEAD
method (which Form Runner doesn't use).