Home / user-249493

Adrian Smith's questions

Martin Hope
Adrian Smith
Asked: 2017-11-29 01:39:54 +0800 CST
  • 5

I am using Apache using Docker on AWS. The Apache listens on port 80 and serves HTTP.

The Apache is behind an AWS ELB load balancer, which listens only on port 443 serving HTTPS.

When I request https://example.com/foo/ (with trailing slash) it works fine, my content is served.

When I request https://example.com/foo (without trailing slash) it redirects to http://example.com/foo/ - that is to say it adds the trailing slash (correctly) but redirects from HTTPS to HTTP (incorrect).

What can I do about that?

My Dockerfile is

FROM httpd:2.4
COPY . /usr/local/apache2/htdocs/

When I do the request via curl:

$ curl -v https://example.com/foo
*   Trying 1.2.3.4...
* TCP_NODELAY set
* Connected to example.com (1.2.3.4) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: example.com
* Server certificate: Amazon
* Server certificate: Amazon Root CA 1
* Server certificate: Starfield Services Root Certificate Authority - G2
> GET /foo HTTP/1.1
> Host: example.com
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Tue, 28 Nov 2017 09:17:26 GMT
< Content-Type: text/html; charset=iso-8859-1
< Content-Length: 247
< Connection: keep-alive
< Server: Apache/2.4.29 (Unix)
< Location: http://example.com/foo/
< 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://example.com/foo/">here</a>.</p>
</body></html>
* Connection #0 to host example.com left intact

Thanks in advance.

apache-2.4
Martin Hope
Adrian Smith
Asked: 2017-11-25 08:09:52 +0800 CST
  • 3

I have a website served by nginx behind an AWS ELB Load Balancer. Only HTTPS is enabled on the load balancer.

Requesting individual files, or directories with a trailing slash, work fine. However, requesting directories without a trailing slash don't work.

The reason is, when I request the directory without the trailing slash, nginx does a redirect to the path with the trailing slash (that's OK), but it also changes from HTTPS to HTTP. The load balancer is configured to only allow HTTPS, so that doesn't work (timeout).

On the nginx logfile, I can see that the request reaches nginx, and that it's nginx that responds with the 301 Permanent Redirect (so it's not e.g. a problem with the load balancer setup).

10.100.10.15 - - [24/Nov/2017:15:41:08 +0000] "GET /admin HTTP/1.1" 301 178 "-" "Wget/1.18 (darwin16.0.0)"

When I request the URL via curl I see the redirect:

$ curl -v https://example.com/admin
*   Trying 1.2.3.4...
* TCP_NODELAY set
* Connected to example.com (1.2.3.4) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: example.com
* Server certificate: Amazon
* Server certificate: Amazon Root CA 1
* Server certificate: Starfield Services Root Certificate Authority - G2
> GET /admin HTTP/1.1
> Host: example.com
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Mon, 27 Nov 2017 09:19:05 GMT
< Content-Type: text/html
< Content-Length: 178
< Connection: keep-alive
< Server: nginx
< Location: http://example.com/admin/
< X-UA-Compatible: IE=Edge
< 
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
* Connection #0 to host example.com left intact

My nginx config file is just 

server {
    root /var/www;
}

The /etc/nginx/nginx.conf is here.

I have tried server_name_in_redirect off but it did not make any difference.

I would like to avoid putting the hostname in the config file, because this is packed into a Docker image which is then deployed on different hosts (QA, Prod, etc.).

I would like nginx to do this redirect, but stay on HTTPS. What can I do?

nginx
Martin Hope
Adrian Smith
Asked: 2016-10-08 02:32:56 +0800 CST
  • 8

I am trying to expose a kubernetes "deployment" via the kubectl expose command, wih a static IP address, on Google Container Engine.

With an ephemeral IP, everything works fine:

kubectl expose deployment my-application \
    --type="LoadBalancer" --port=80 --target-port=8080

I use kubectl get services and wait a few minutes to see the ephemeral IP having been assigned. I enter the IP in my browser and I see the applicaiton, i.e. everything works.

However, when I do the following:

  1. Create a static IP address using the gcloud web interface (Networking -> External IP addresses -> Reserve Static IP address)

  2. Re-create the service with the same command as above but with the extra --load-balancer-ip option

    kubectl expose deployment my-application \
    --type="LoadBalancer" --port=80 --target-port=8080 \
    --load-balancer-ip='1.2.3.4'   # IP as assigned by web interface above

The command is successful, but the application is not reachable under that IP address, and when I use the following command:

$ kubectl get services
NAME         CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
endpoints    10.119.247.39   <pending>     80/TCP    23m
kubernetes   10.119.240.1    <none>        443/TCP   1d

I see that the EXTERNAL-IP is still <pending> although I've waited 23 minutes so far.

What am I doing wrong?

kubernetes gcloud
Martin Hope
Adrian Smith
Asked: 2016-10-06 06:49:15 +0800 CST
  • 0

I have installed the Google Cloud tools on my Linux box as described here with:

  1. curl https://sdk.cloud.google.com | sudo bash
  2. sudo gcloud init
  3. sudo gcloud components install kubectl beta

So far so good. However when I run kubectl I get the error

$ kubectl cluster-info
error: failed to negotiate an api version; server supports: map[], client supports: map[batch/v2alpha1:{} policy/v1alpha1:{} rbac.authorization.k8s.io/v1alpha1:{} authentication.k8s.io/v1beta1:{} authorization.k8s.io/v1beta1:{} componentconfig/v1alpha1:{} autoscaling/v1:{} v1:{} apps/v1alpha1:{} batch/v1:{} extensions/v1beta1:{} federation/v1beta1:{}]

Do you have any idea what I'm doing wrong or what I have to configure?

kubernetes gcloud