stokito commented on pull request #324: URL: https://github.com/apache/tomcat/pull/324#issuecomment-661083626
> The format of the ETag is opaque, it is up to the caching instance to generate one Yes, you are right. In the same time too smart client may not send Ranges requests to download part of the file if it sees Weak ETag. This more semantical issue. But the main goal to to make ETag interoperable between different servers. > We cannot guarantee any strong ETags because WebResource is an interface which does not guarantee to properly return required information. But we can't guarantee even a Weak ETag ether. Anyway this is a default implementation and subclasses are free to override the method and return anything they need. I checked Catalina sources and there is two WebResource implementors: File and Jar. Both of them will be fine. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
