如何在Traefik中配置类似Nginx的proxy_set_header Authorization头实现自动认证

Traefik完全支持类似Nginx的proxy_set_header自定义请求头注入能力，可通过headers中间件实现自动注入Authorization头，无需用户手动登录Komga，具体实现方案如下：

前置准备 #

先将你的Komga登录账号密码按账号:密码的格式转换为Base64编码，示例中的king:isnaked转换后为a2luZzppc25ha2Vk，可直接通过命令echo -n "账号:密码" | base64生成符合要求的编码值。

方案1：Docker 动态标签配置（最常用场景） #

在Komga服务的docker-compose配置中添加以下Traefik标签即可：

services:
  komga:
    image: gotson/komga:latest
    labels:
      - "traefik.enable=true"
      # 按需修改你的域名规则
      - "traefik.http.routers.komga.rule=Host(`komga.yourdomain.com`)"
      - "traefik.http.routers.komga.entrypoints=websecure"
      - "traefik.http.routers.komga.tls=true"
      # 注入Authorization认证头
      - "traefik.http.middlewares.komga-add-auth.headers.customrequestheaders.Authorization=Basic a2luZzppc25ha2Vk"
      # 绑定中间件到路由
      - "traefik.http.routers.komga.middlewares=komga-add-auth@docker"
      # 替换为Komga实际监听端口
      - "traefik.http.services.komga.loadbalancer.server.port=8080"

方案2：Kubernetes IngressRoute 配置 #

先创建头注入中间件，再绑定到Komga的IngressRoute即可：

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: komga-add-auth
  namespace: your-namespace
spec:
  headers:
    customRequestHeaders:
      Authorization: "Basic a2luZzppc25ha2Vk"
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: komga
  namespace: your-namespace
spec:
  entryPoints:
    - websecure
  routes:
    - match: Host(`komga.yourdomain.com`)
      kind: Rule
      services:
        - name: komga
          port: 8080
      middlewares:
        - name: komga-add-auth
  tls:
    certResolver: your-cert-resolver

方案3：静态YAML配置文件（适合二进制部署Traefik场景） #

直接在Traefik的静态配置文件中添加以下规则：

http:
  routers:
    komga:
      rule: "Host(`komga.yourdomain.com`)"
      service: komga
      middlewares:
        - komga-add-auth
      tls: {}

  services:
    komga:
      loadBalancer:
        servers:
          - url: "http://6.6.6.6:8080" # 替换为你的Komga实际访问地址

  middlewares:
    komga-add-auth:
      headers:
        customRequestHeaders:
          Authorization: "Basic a2luZzppc25ha2Vk"

注意事项 #

• 如果同时配置了Traefik自带的基础认证中间件，请确保优先级，避免Authorization头被覆盖。
• 该方案属于硬编码身份凭证，仅推荐在内部可信环境使用，对外暴露的场景请额外做好访问权限管控，避免凭证泄露。

内容的提问来源于stack exchange，提问作者James Adams