In nginx, the difference between ip_hash and url_hash

Recently looking at the load balancing of nginx, I found that in order to solve the session problem of nginx, there are two methods, namely ip_hash and url_hash. ip_hash maintains the session based on ip, while url_hash is based on url address. The advantage of url_hash is that it can improve The efficiency of the back-end cache server, such as improving the efficiency of Squid, but the disadvantage is that when the back-end server goes down, url_hash will not automatically jump to other cache servers, but will return a 503 error to the user. What I want to ask is , does ip_hash solve this problem, will it jump to other machines, or will it still return a 503 error? What is the difference between ip_hash and url_hash, and can nginx solve both the session problem and the backend problem? Server health check issue. I remember that Squid can perform health checks and maintain sessions.

Or you can use memcached to maintain the session and achieve session sharing without worrying about the session being dropped

Copyright statement: This article is an original article by the blogger and may not be reproduced without the permission of the blogger.

The above introduces the difference between ip_hash and url_hash in nginx, including the relevant content. I hope it will be helpful to friends who are interested in PHP tutorials.