Site Redirection in Traefik using RedirectRegex Middleware

Wed, 06 Nov 2019 00:00:00 +0000

Implementing URL redirection in Traefik works like normal service with middleware processing. To setup redirection, setup the base router with middleware, and some dummy service.

http:
 routers:
 shop-secure:
 entryPoints:
 - "web-fe-secure"
 rule: "Host(`shop.moe.ph`)"
 middlewares:
 - "shopredirect"
 service: "shop-redirect"
 tls: {}

For middleware, you will need to use redirectRegex middleware processor. Just put the URL that you want to process, and it’s replacement.

http:
 middlewares:
 shopredirect:
 redirectRegex:
 regex: "^https://shop.moe.ph/(.*)"
 replacement: "https://shopee.ph/moe_ph"

Unfortunately, this router-middleware processing of URL redirection still needs service block. If you are redirecting your URL to another domain, just put a dummy service.

http:
 services:
 shop-redirect:
 loadBalancer:
 servers:
 - url: "http://localhost/"

To do more complex redirection, just check the Traefik’s documentation.

King Traefik 2.0, Queen Django, and Jack passHostHeader

Fri, 30 Aug 2019 00:00:00 +0000

Deploying Django application means deploying it behind Nginx webserver most of the time. We are also using this setup. Deploying it this way is easy, since you need to set proxy_pass and proxy_set_header.

The only problem with this setup is when you only have 1 Nginx webserver for multiple Django backend. When you deploy new Django apps, you need to add new setting for it and restart the server. You might be able to reload it by sending SIGHUP to Nginx master process, but we are using container, so it’s hassle. You also need to reload it every time you edited something.

That’s when we look into alternative reverse proxy. We look for more cloud-native proxy, and that’s when we found about Traefik. Traefik is a cloud native edge router. It has integrations into multiple cluster technology. It also supports live reload of configuration files for dynamic settings. We are using podman to manage containers, so we are utilizing the dynamic file reload.

We start playing with Traefik, and use version 2. Tinkering with Traefik is not that easy if you’re not familiar with the earlier version.

The setting that really ticked our testing is passing the proxy host header to backend. The first settings that we look through are middleware headers settings of Traefik. This is the most logical place to look first, if you are playing with headers, right? We played with these settings.

Seems okay, but it didn’t actually work. The host header is still not pass to the backend. I hold some grudge to Traefik this time, then I realized that I need to check the settings for earlier version. There are Traefik settings scattered through Github, so I found this boolean setting.

passHostHeader = true

I guess this setting should be present to Traefik 2.0. After checking the dynamic configuration reference, I found this setting.

services:
 Service01:
 loadBalancer:
 passHostHeader: true

I set this to true and the backend is now responding.

I guess everyone should know about this setting.

Traefik | blog.moe.ph

Site Redirection in Traefik using RedirectRegex Middleware

King Traefik 2.0, Queen Django, and Jack passHostHeader