CODEWITHSUNDEEP
load-balancinggoogle-compute-enginegcloud
Karel Jakubec
Karel Jakubec

Reputation: 452

Use 301 to redirect http to http(s) behind google cloud load balancer

I have a service running in google cloud, basically several machines behind google http(s) load balancer. I've setup two balancing rules, one for http:// and one for https://. The thing I want to do is to redirect all http:// requests to https://. There is an apache running on each node so I make configuration like:

<VirtualHost *:80>
    ServerName my.app.com

    Redirect permanent / https://my.app.com
</VirtualHost>


<VirtualHost *:443>
    ServerName my.app.com
    SSLEngine On
    ....
</VirtualHost>

This should make apache to return 301 in case of somebody is accessing plain http. This worked fine till I moved behind the google http load balancer since then I am getting 400 and:

Bad Request

Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please.

Apache/2.4.10 (Debian) Server at my.app.com Port 443

It looks like google load balancer consumes the 301 and redirects the plain http request to https endpoint instead of forwarding the 301 to the client. I have not found any settings regarding 3XX forwarding in the google load balancer settings. Has anyone made this kind of setup working?

Upvotes: 3

Views: 2741

Answers (1)

Karel Jakubec
Karel Jakubec

Reputation: 452

Ok, I will answer myself, maybe someone find this useful later.

Currently it is not possible to achieve forwarding of 301 using Google HTTP Load balancing to client. Load balancer will see the 301 and will send your plain HTTP request to the adress where 301 points - which is the same server, but port 443. Your server expects HTTPS packet but HTTP arrives so it fails.

Solution which is currently working for us - use Haproxy or Nginx as reverse proxy instead of Google HTTP Load Balancer.

Upvotes: 4

Related Questions