When the "My Data (DIY)" app makes a subsequent HTTP request to the configured source, does it send the ETag value it received in the previous request? (As in that if this is indeed supported, I can have my source return a code 304 if the data hasn't changed since it was last retrieved without having to send the entire or an entirely-duplicated payload.)
jm6600
Hi,
When the "My Data (DIY)" app makes a subsequent HTTP request to the configured source, does it send the ETag value it received in the previous request? (As in that if this is indeed supported, I can have my source return a code 304 if the data hasn't changed since it was last retrieved without having to send the entire or an entirely-duplicated payload.)