load-balancing

I am trying to force all http requests to https requests and I am facing the problem as elastic load balancer not populating x-forwarded-proto header in the request. This is the code I am using and it is causing redirect loop because of this. How would I fix this problem? app.use (function (req, res, next) { console.log('Request headers = ' + JSON.stringify(req.headers)); console.log('Request protocol = ' + JSON.stringify(req.protocol)); var schema = (req.headers['x-forwarded-proto'] || '').toLowerCase(); if (schema === 'https') { next(); } else { res.redirect('https://' + req.headers.host +

We're using amazon web service for a business application which is using node.js server and mongodb as database. Currently the node.js server is runing on a EC2 medium instance. And we're keeping our mongodb database in a separate micro instance. Now we want to deploy replica set in our mongodb database, so that if the mongodb gets locked or unavailble, we still can run our database and get data from it. So we're trying to keep each member of the replica set in separate instances, so that we can get data from the database even if the instance of the primary memeber shuts down. Now, I want to

In Amazon, I am attempting to create a cname for a domain, example.com to a load balancer in Route 53 Examplecom-1058462749.us-west-2.elb.amazonaws.com But when I try to save the record, I get this error: RRSet of type CNAME with DNS name example.com. is not permitted at apex in zone example.com. And when I try to make it an A record, I get a similar issue: The record set could not be saved because: - The Value field contains invalid characters or is in an invalid format. Because the public DNS of the load balancer is not an ipv4 address. What am I doing wrong? How can i get example.com to

I have created a cluster using the google cloud plateform (container engine) and deployed a pod using the following yaml file: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: deployment-name spec: replicas: 1 template: metadata: name: pod-name labels: app: app-label spec: containers: - name: container-name image: gcr.io/project-id/image-name resources: requests: cpu: 1 ports: - name: port80 containerPort: 80 - name: port443 containerPort: 443 - name: port6001 containerPort: 6001 Then I want to create a service that enables the pod to listen on all these ports. I know that he

GCP provides two load balancers namely Network and HTTP(s) where the former works on layer 4 and the later works on layer 7 . There is also a documentation which states that even HTTP traffic can be load balanced by a network load balancer. This slightly confuses which load balancer to choose for a web app in GCP. It is better to understand the differences before selecting one for the project. What are the differences between them based on the workflow , setup , region/zone based, options for session affinity , and other settings? Lakshman Diwaakar Network load balancer Vs HTTP(s) Load

Using ASP.Net MVC v2.0, I am starting to research the use of the Html.AntiForgeryToken() method when submitting forms that process data. I can see it sets a hidden value in the form HTML and it sets the same value in a session cookie. The question is will different web servers in a load balanced configuration create the same token in the HTML forms? It seems if they don't then the cookie and hidden form value wouldn't match and we would have a problem. Before I get into actually testing this in a LB configuration, wanted to check if anyone already has experience with this? Thanks, Paul Levi If

Are there any possible issues with using the default Forms Authentication (see below) on Load Balanced servers? If there can be, what can I do to prevent the issues. <authentication mode="Forms"> <forms loginUrl="~/Login/" protection="All" timeout="30" /> </authentication> Can I use cookies (used by default)? Do I have to go cookieless? etc... Also, does Microsoft (or VMWare) have a VirtualPC download that is an instant Load Balanced testing environment? There is one issue. The cookies are encrypted and validated using the machine key and the validation key (that's what protection="All" means)