You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ETags are a core feature of web servers that users should expect to work out of the box. This should be a non-middleware feature baked into either Application or HTTPRequest classes, with the option to disable or swap implementations if the user so chooses.
The text was updated successfully, but these errors were encountered:
Yes, one I mentioned above is for static content.
Dynamic content best when generate ETags itself, cause it can do it the most effective way - based on version of doc, or hash generated on doc save, or similar. Otherwise you have to calculate some kind of hash on every response - performance impact.
ETags are a core feature of web servers that users should expect to work out of the box. This should be a non-middleware feature baked into either Application or HTTPRequest classes, with the option to disable or swap implementations if the user so chooses.
The text was updated successfully, but these errors were encountered: