load-balancing

问题 I have a Java servlet that sits behind a hardware load balancer. The load balancer only allows https requests. The problem is when I get the request in the servlet, I can only see http, it seems it has been decrypted by the time it gets to the servlet, which makes sense because the servlet should not worry about security. When I want to send a redirect in servlet, however, the request will be blocked by the load balancer because it will be a http request. I read about some solutions and they

问题 I have a Java servlet that sits behind a hardware load balancer. The load balancer only allows https requests. The problem is when I get the request in the servlet, I can only see http, it seems it has been decrypted by the time it gets to the servlet, which makes sense because the servlet should not worry about security. When I want to send a redirect in servlet, however, the request will be blocked by the load balancer because it will be a http request. I read about some solutions and they

问题 I am attempting to put a Load Balancer in front of a Turn Server for use with WebRTC. I am using one turn server in my examples below until I get the load balancer working. The turn server requires multiple ports including one UDP as listed below: TCP 80 TCP 443 TCP 3478 TCP 3479 UDP 3478 I have attempted to place an Amazon Elastic Load Balancer (AWS ELB) in front of the Turn Server, but it does not support the UDP port. So I am now running Ubuntu on an EC2 Instance with all these ports open

问题 I know it is possible to make connections sticky based on url a parameter: https://serverfault.com/questions/495049/using-url-parameters-for-load-balancing-with-haproxy?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa Is it also possible to do it based on an ID in the url path? If my url is: /objects/:objectId Can I somehow use that :objectId to make the connection sticky? EDIT I was able to load balance making the request sticky on the url path using the configuration

问题 I need to prevent users from accessing the site through the External IP Address on Compute Engine, they should can access site only via domain name (www.some-domain.com), not the IP Address itself. Let says the instance's IP Address of the Compute Engine is A.A.A.A. I am using Load Balancer to redirect it to secure connection, with these settings: Frontend HTTP : B.B.B.B:80 HTTPS : B.B.B.B:443 Backend Redirected to the active instance And I pointing the DNS (A) to B.B.B.B. Now, I am able to

问题 Scenario: I have a Google Compute Engine instance exposing a web application via HTTP port 80 and I can access it directly using an external IP address. Then, I added a HTTP load balancer with a health check and afterwards, I could access the web application via the load balancer without any problem. Now, if I remove the external IP address of the compute instance, the health check of the load balancer starts failing. I read [1] and added a firewall rule to allow health check probes coming

问题 I have a nginx loadbalancer in front of two tomcat instances each contains a spring boot application. Each spring boot application executes a batch that writes data in a database. The batch executes every day at 1am. The problem is that both instances execute the batch simultaniously which i don't want. Is there a way to keep the batchs deployed in two instances and tell tomcat or nginx to start the batch in master server (and the slave server doesn't run the batch). If one of the servers

问题 I configured apache proxypass and it's working but not loading images, javascript, CSS etc... I want to proxypass to another server, not localhost. Below is my configuration. see error image <VirtualHost *:80> ServerName app.server.com DocumentRoot /var/www/html/subdomain RewriteEngine on ProxyRequests Off ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined ProxyPass /apm http://192.168.1.102:9999/ ProxyPassReverse /apm http://192.168.1.102:9999/ </virtualHost

问题 A backend service happens to be returning Status 404 on the health check path of the Load Balancer. When I browse to the Load Balancer's domain name, I get "Error: Server Error/ The server encountered a temporary error", and the logs show "type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry" statusDetails: "failed_to_pick_backend" , which makes sense. When I browse to the Load Balancer's Static IP, my browser shows the 404 Error Message which the underlying Kubernetes Pod

问题 We are in the process of setting up a service on GCP that will serve requests from both the internet and from other services inside of our VPC. We already have a global load-balancer setup and want all traffic to our new service to be load-balanced as well. Is it advisable to have our internal services use the global LB address when trying to reach the new service? Or should we be setting up internal LBs behind the global LB for internal services to use? If we were to use the global LB for