https://bz.apache.org/bugzilla/show_bug.cgi?id=64616
--- Comment #4 from Sergey Ponomarev <stok...@gmail.com> --- I also thought to make ETag configurable like in Apache HTTPD but in fact for clients this is still opaque value and the Nginx is not configurable anyway while Apache Htttpd can be configured to be compliant with Nginx. I'm asking for this because this is a real issue for me. I developing a new service (https://github.com/yurt-page coming soon) that will use several servers: * WiFi router with a small blog engine running on BusyBox httpd * Tomcat on PC with the same blog engine plus admin panel. When PC is online requests will be redirected from router to PC. * Front server with Nginx with basic WAF, cache offload and static IP (kind of Cloudflare). So here the problem with ETag is extremely important for success. BusyBox not even had support of ETag so I sent a patch to to them http://lists.busybox.net/pipermail/busybox/2020-July/088102.html And I'm pretty sure that I'm not the only one who needs the ETag format interop. BTW the new ETag format while generated at the same speed are 14 bytes long while old used 22. Seems like not a big deal but they are transmitted on each request. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
