入口 nginx 从 www 重定向到 https答案

【问题标题】：ingress nginx redirect from www to https入口 nginx 从 www 重定向到 https
【发布时间】：2020-04-01 11:11:44
【问题描述】：

我正在尝试使用 ingress-nginx 将 http://www... 和 https://www... 重定向到 https://...。我怎样才能做到这一点？

我尝试使用注释nginx.ingress.kubernetes.io/server-snippet 和nginx.ingress.kubernetes.io/configuration-snippet 添加以下自定义配置：

# 1
if($host = "www.example.com") {
    return 308 https://example.com$request_uri;
}

# 2
server {
    server_name www.example.com;
    return 308 https://example.com$request_uri;
}

# 3
server_name www.example.com;
return 308 https://example.com$request_uri;

但我在 #1 的 nginx 控制器日志中收到错误：

2019/12/07 20:58:47 [emerg] 48898#48898: unknown directive "if($host" in /tmp/nginx-cfg775816039:418
nginx: [emerg] unknown directive "if($host" in /tmp/nginx-cfg775816039:418
nginx: configuration file /tmp/nginx-cfg775816039 test failed

对于#2，我收到一个错误，即在该位置不允许服务器块，使用#3 会导致无限重定向。我的入口 yaml 如下所示：

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-nginx
  annotations:
    kubernetes.io/ingress.class: "nginx"
    kubernetes.io/ingress.global-static-ip-name: "example-com"
    nginx.ingress.kubernetes.io/rewrite-target: "/"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "86400s"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "86400s"
    nginx.ingress.kubernetes.io/proxy-body-size: "100m"
    nginx.ingress.kubernetes.io/limit-rps: "20"
    nginx.ingress.kubernetes.io/client-max-body-size: "100m"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      # see above
spec:
  tls:
  - hosts:
      - example.com
    secretName: certificate-secret
  rules:
  - host: sub.example.com
    http:
      paths:
      - backend:
          serviceName: service-sub
          servicePort: 1234
# more subdomains here
  - host: example.com
    http:
      paths:
      - backend:
          serviceName: service-example
          servicePort: 1235
  - host: "*.example.com"
    http:
      paths:
      - backend:
          serviceName: service-example-wildcard
          servicePort: 1236

我也尝试设置nginx.ingress.kubernetes.io/from-to-www-redirect: "true" 注释，但这会导致不同的错误：

2019/12/07 21:20:34 [emerg] 51558#51558: invalid server name or wildcard "www.*.example.com" on 0.0.0.0:80
nginx: [emerg] invalid server name or wildcard "www.*.example" on 0.0.0.0:80
nginx: configuration file /tmp/nginx-cfg164546048 test failed

【问题讨论】：

您确定可以在 Ingress host: 名称中使用通配符吗？我以前从未见过这种情况，the reference documentation 根本没有提到这种行为做任何事情，更不用说有建设性的事情了。我想一个更好的问题：当你有那个通配符时，它是否达到了你的预期，与你当前的重定向问题无关？
对于为什么"if($host" 表示错误，甚至不值得创建一个答案：这是因为您没有在if 和( 之间放置空格
是的，通配符主机有效。谢谢你的回答我会用空格测试它;）

标签： nginx kubernetes configuration kubernetes-ingress nginx-ingress

【解决方案1】：

好的，我明白了。 if 之后的缺失空间已修复。谢谢你 mdaniel :) 这是一个工作配置，可以将任何内容重定向到 https://... 而没有 www：

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-nginx-integration
  namespace: integration
  annotations:
    kubernetes.io/ingress.class: "nginx"
    kubernetes.io/ingress.global-static-ip-name: "example-com"
    nginx.ingress.kubernetes.io/rewrite-target: "/"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "86400s"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "86400s"
    nginx.ingress.kubernetes.io/proxy-body-size: "100m"
    nginx.ingress.kubernetes.io/limit-rps: "20"
    nginx.ingress.kubernetes.io/client-max-body-size: "100m"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($host = "www.example.com") {
          return 308 https://example.com$request_uri;
      }
spec:
  tls:
  - hosts:
      - example.com
    secretName: certificate-integration-secret
  rules:
  - host: subdomain.example.com
    http:
      paths:
      - backend:
          serviceName: service-emviwiki
          servicePort: 4000
  # ... more rules, NO www here

【讨论】：