Load balancing based on URLs

This provides only one way to direct the interface for location distribution. The simplest configuration makes it clear that the interface is directed for distribution and is not explained for other configurations. such as requesting two url:1), Www.000.com/sale

2),www.000.com/matchmaker

 

2. #user nobody;
4. Worker_processes 1;
8. Events {
10. Worker_connections 1024;
12. }
16. http {
18. Include Mime.types;
20. Default_type Application/octet-stream;
22. Sendfile on;
24. Keepalive_timeout 65;
26. Upstream Sale {
28. server 192.168.1.100:8000 max_fails=2;
30. }
34. Upstream Matchmaker {
36. Server 192.168.1.200:8080 max_fails=2;
38. }
42. Server {
44. Listen;
46. server_name www.000.com;
48. Location/sale {
50. Root/www
52. Proxy_pass Http://sale;
54. }
58. Location/matchmaker {
60. Root/www
62. Proxy_pass Http://matchmaker;
64. }
66. }
68. }

Description: When the request/HTTP/ www.000.comWhen/sale arrives, listen for the domain name on port 80 port www.000.comAccording to the location match to sale, and then according to the field Proxy_pass Http://sale to find the corresponding upstream, then the request will arrive 192.168.1.100:8000 this machine. It's done. Load balancing based on URL directed forwarding

Load balancing based on URLs