Hi Actually this "problem" was not introduced in this version, it exists for a long time.
The scene is using haproxy for LB http requests to different cache server based on uri hash. This works well for normal request. But when end-users access via a http proxy, the uri changed. The first line of a normal request: GET /1.jpg HTTP/1.1 The first line of a request via some http proxy: GET http://www.google.com/1.jpg HTTP/1.1 The result is the same two object hashed to two different cache server [A and B]. But this is not the worst case, since only a little bit storage wasted. The worst case is if web administrator update the origian 1.jpg and remove 1.jpg in cache server A. The out-of-date object stored in cache server B will never be removed/updated. I am not sure this is a bug or not, but I guess this might be one problem. -- *Fred Hu* *Best Regards*
