No problem if you disable the “Cache control header optimizations”. If you enable it (by default it is enabled) Dynatrace adds an entry to the Etag HTTP header and will update this Etag with each modification of the application configuration. So if you make any modifications to the Application configuration (such as user tag definition), it may take some time to propagate these changed to clients.
Actually, we have encountered an issue with the Cache control since application returned the Etag header but it was empty (just a single space). Since Dynatrace added another ID to the Etag header, the returned response had Etag set and this led to serious issues with application responses being cached. Unfortunately, this behaviour was caused by a badly designed application (It should not return Etag header with an empty value).