Hi Lucas, Thanks a lot for the suggestion. We were already using that solution but a strange behavior occurred (see opening post). The first request uses an expected MD5 hash of the KEY, and the client will keep using that hash (the MISS/HIT header is accurate). However, requests from other clients will make Nginx use a different (unknown) MD5 hash for the exact same content and KEY. The cache file contains a row with "KEY: ..." that matches the expected KEY and KEY for other MD5 hashes.
Do you have an idea what may cause this behavior? Best Regards, Jan Jaap Posted at Nginx Forum: https://forum.nginx.org/read.php?2,270604,270661#msg-270661 _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
