logo
down
shadow

GCP HTTP Load Balancer returns 502 error if POST data is large


GCP HTTP Load Balancer returns 502 error if POST data is large

By : newbie2778930
Date : November 21 2020, 11:01 PM
To fix the issue you can do reference from this question Curl to Google Compute load balancer gets error 502
It's because CURL has default value when request large POST body defining header as Expect: 100-continue
code :


Share : facebook icon twitter icon
Calling web service that sits on a load balancer with jax-ws returns at http status of 302, but when I use SoapUI it wor

Calling web service that sits on a load balancer with jax-ws returns at http status of 302, but when I use SoapUI it wor


By : Lucian B.
Date : March 29 2020, 07:55 AM
around this issue So after lots of investigation I finally figured out what the problem was. It was all down to redirecting from http to https. From articles I found on the web (can't remember the urls anymore), is that the libraries that the wsdl2java and wsimport stub generators use to do the webservice communication don't allow a http to https redirect follow due to security reasons.
So even though I was generating the stubs from a https wsdl location ie. https://wsdl.location.com?wsdl, when I ran the code to do a webservice call, it was trying to make the call to http://wsdl.location.com which resulted in a redirect request to https://wsdl.location.com, But the http library does not allow that. So it just forwards the 302 http code up as an exception.
code :
NotificationWebService service = new NotificationWebService();
NotificationWebServiceSoap serviceSoap = service.getNotificationWebServiceSoap();

BindingProvider bindingProvider = (BindingProvider) serviceSoap;
bindingProvider.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "https://wsdl.location.com");

String xmlString = serviceSoap.getRSAPublicKeyXMLString();
How to setup dual http and https servers behind a load balancer like elastic balancer

How to setup dual http and https servers behind a load balancer like elastic balancer


By : ifezuoke onyeka
Date : March 29 2020, 07:55 AM
will help you
Like you stated, you may configure the ELB to forward all HTTPS and HTTP traffic to your applications http server, eliminating the need to handle any https configuration in your application. You may refer to the 'X-Forwarded-Proto' header to detect whether the request is coming though as http vs https.
code :
app.use(req, res, next) {
  if(req.headers['x-forwarded-proto'] == 'http' && process.env.NODE_ENV!=="development"){
    res.redirect('https://' + req.headers.host + req.path);
  } else {
    next();
  }
}
Google cloud HTTP load balancer always returns unhealthy instance for meteor app

Google cloud HTTP load balancer always returns unhealthy instance for meteor app


By : Chirag Sampat
Date : March 29 2020, 07:55 AM
this will help In order to use HTTP load balancing on Google Cloud with Kubernetes, you have to take a slightly different approach than for network load balancing, due to the current lack of built-in support for HTTP balancing.
I suspect you created your service in step 3 with type: LoadBalancer. This won't work properly because of how the LoadBalancer type is implemented, which causes the service to be available only on the network forwarding rule's IP address, rather than on each host's IP address.
GCP: Directing traffic from Global HTTP Load Balancer to istio internal load balancer

GCP: Directing traffic from Global HTTP Load Balancer to istio internal load balancer


By : user3323971
Date : March 29 2020, 07:55 AM
will help you You can set up a Global Loadbalancer on top of Istio. However, you can't reach the TCP load balancer automatically set up by Istio Ingress Gateway.
This Ingress Gateway, is a K8S service which expose NodePorts. You can get them with this commands:
code :
# For HTTP
kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="http2")].nodePort}'

# For HTTPS
kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="https")].nodePort}'
HTTP Load Balancer cuts out part of a large request body

HTTP Load Balancer cuts out part of a large request body


By : Shelbys_Dad
Date : March 29 2020, 07:55 AM
it fixes the issue The problem might originate in the fact that GCE HTTP load balancer doesn't support HTTP 100 Continue requests, which can affect multipart POST requests. The solution lies either in not using multipart, or using GCE network load balancing (which might or might not offer what you need).
shadow
Privacy Policy - Terms - Contact Us © soohba.com