I have nginx running in a container behind Traefik, and I'm trying to redirect any http to https using Traefik middleware.
If I browse to https://domain-name/website-name I can see my container, but if I browse to http://domain-name/website-name, I get a 404 error.
Below is my config file for website-name:
http:
routers:
entrypoints:
- web
- web-secure
tls: true
rule: "PathPrefix(`/website-name`)"
middlewares:
- "http-redirect"
service: "website-name"
middlewares:
http-redirect:
regex: "http://domain-name/(.*)"
replacement: "https://domain-name/$1"
services:
website-name:
loadBalancer:
servers:
- url: http://website-name:80
Why won't http redirect to https with this setup? It only recognizes https.
For example if I change the http-redirect code to:
http-redirect:
redirectRegex:
regex: "https://domain-name/(.*)"
replacement: "https://$1?test"
This works and redirects https://domain-name/website-name to https://domain-name/website-name?test, but for some reason http won't work.
http://domain-name/website-name gives me a 404 error. And, it is not a 404 error produced by nginx. So it is not even routing to the container.
Related
Kind cluster with nginx ingress, 80 443 ports are extramapped. For deploying Jenkins yaml files from official tutorial where used, except from service type - i use ClusterIP k8s service. Ingress rule applies for service and Jenkins makes uri substituion, so resulted uri isn' found (404)
uri substitution
ingress rule i apply
"/" ingress rule path leads to this "login?from=%2F"
"admin" ingress rule path leads to "login?from=%2Fadmin", but it's still 404 !!!
resources: {}
env:
- name: JENKINS_OPTS
value: --prefix=/jenkins
this part ^ in deployment doesn't help neither
old articles about ingress rules for Jenkins read, and rules from these articles are simple but old (without pathType), doesn't work now
annotations:
nginx.ingress.kubernetes.io/app-root: /
nginx.ingress.kubernetes.io/rewrite-target: /$2
this part ^ leads to http://diploma/login?from=%2F - and still 404
curl says it's HTTP/1.1 403 Forbidden - X-Content-Type-Options: nosniff
Set-Cookie: JSESSIONID.5c694702=node0vvv1jgg0mr5w1c63m7fciri1e217.node0; Path=/; HttpOnly
Any ideas ?
Is there a way to set up Traefik as a reverse proxy for S3 Static website hosting?
I tried by using the file provider as follows:
# http routing section
http:
routers:
# Define a connection between requests and services
to-site:
rule: "PathPrefix(`/site`)"
middlewares:
- site-stripprefix
service: site
middlewares:
site-stripprefix:
stripPrefix:
prefixes:
- "/site"
services:
# Define how to reach an existing service on our infrastructure
site:
loadBalancer:
servers:
- url: http://mysite.s3-website-us-east-1.amazonaws.com
It redirects me to https://aws.amazon.com/s3/.
I can't find a setup example of traefik-v2 , only for Nginx.
After setting up the proxy with Nginx I figure this out.
I think Traefik is much more elegant.
For anyone how will need it:
# http routing section
http:
routers:
# Define a connection between requests and services
to-site:
rule: "PathPrefix(`/site`)"
middlewares:
- site-stripprefix
- site-add-headers
service: site
middlewares:
site-stripprefix:
stripPrefix:
prefixes:
- "/site"
site-add-headers:
headers:
customRequestHeaders:
Host: "mysite"
services:
# Define how to reach an existing service on our infrastructure
site:
loadBalancer:
passHostHeader: false
servers:
- url: http://mysite.s3-website-us-east-1.amazonaws.com
I'm trying to setup a route do a basic 301 redirect with the added benefit of supporting both HTTP and HTTPS requests. Expected results would be that requests to http://subdom.domain.org or https://subdom.domain.org would receive a 301 and be forwarded to https://othersub.domain.org/route. Actual results is that https://subdom.domain.org 301's as expected, but http://subdom.domain.org 404's. With the config, you can see I've tried doing both an elevate to HTTPS with the hopes that the rule might be caught there, but with the way the middleware is configured, I would expect it would work in either scenario.
Here's my current config:
http:
routers:
subdom.domain.org:
entryPoints:
- web
- web-secure
middlewares:
- https-redirect # I've tried with this on and off
- sudbdom-redirect
service: dummy
rule: Host(`subdom.domain.org`)
tls:
certResolver: letsEncryptResolver
middlewares:
https-redirect:
redirectScheme:
scheme: https
subdom-redirect:
redirectRegex:
regex: ".*"
replacement: "https://othersub.domain.org/route"
permanent: true
services:
dummy:
loadBalancer:
servers:
- url: localhost
I was originally having trouble matching specific regex patterns for the redirect, but in realizing I didn't really need to scope the pattern at all given that I'm applying it per route, a wildcard match seems to work quite well there. Any thoughts or suggestions are appreciated. Thanks!
You should try to make 2 different router one for web entry point where you can perform redirection and 2rd one for redirectRegex where you can redirect your application to different url.
Following TLS section from official documentation:
When a TLS section is specified, it instructs Traefik that the current router is dedicated to HTTPS requests only (and that the router should ignore HTTP (non TLS) requests).
Solutions:
1. Define separate routers (for http and https), but it noisy for multiple services.
If you need to define the same route for both HTTP and HTTPS requests, you will need to define two different routers: one with the tls section, one without.
Example from documentation
2. Disable TLS for router
traefik.http.routers.YOUR-SERVICE.tls=false
Example:
services:
mailhog:
image: mailhog/mailhog
networks:
- traefik-public
deploy:
placement:
constraints:
- node.role != manager
labels:
- "traefik.enable=true"
- "traefik.http.routers.mailhog.rule=Host(`mailhog.somehost.ru`)"
- "traefik.http.routers.mailhog.service=mailhog"
- "traefik.http.routers.mailhog.entrypoints=web,websecure"
# Should be false
- "traefik.http.routers.mailhog.tls=false"
- "traefik.http.middlewares.redirectos.redirectscheme.scheme=https"
- "traefik.http.routers.mailhog.middlewares=redirectos"
- "traefik.http.services.mailhog.loadbalancer.server.port=8025"
- "traefik.tags=traefik-public"
- "traefik.docker.network=traefik-public"
I am using traefik 2.0.2 as reverse proxy in front of some services. One backend services is returning a redirect response (302), where the location header contains the absolute redirected url. The url of the backend is not reachable from the outside, how can I rewrite the location to go through the reverse proxy again?
E.g. a client requests http://my-domain/foo and receives a 302 response with location header containing http://backend:8080/foo/bar/, which of course will not work.
I am looking for something similar to ProxyPassReverse of apache mod_proxy. I have read through the available middlewares of traefik, but nothing seems to fit my requirement.
My simplified configuration:
# traefik.yml
entryPoints:
web:
address: ":80"
providers:
file:
filename: "dynamic-conf.yml"
# dynamic-conf.yml
http:
routers:
router1:
entryPoints:
- web
service: service1
rule: "PathPrefix(`/foo`)"
services:
service1
loadBalancer:
servers:
- url: http://backend:8080
I did not find an option to rewrite the location header of a service response using traefik.
A feature request to replaceResponseHeaders exists.
My (temporary) solution is to perform the redirection in traefik using the RedirectRegex middleware, such that the backend service does not need to response with a redirect.
The updated configuration would look like this:
# dynamic-conf.yml
http:
routers:
router1:
entryPoints:
- web
service: service1
rule: "PathPrefix(`/foo`)"
middlewares:
- my-redirect
middlewares:
my-redirect: # Workaround for service1 redirection
redirectRegex:
regex: "^https?://[^/]+/foo/?$"
replacement: "/foo/webapp/"
services:
service1
loadBalancer:
servers:
- url: http://backend:8080
I had the same issue as you, could not resolve it with your solution, but now, with the traefik plugins, we can:
Static config:
pilot:
token: "xxxx"
experimental:
plugins:
rewriteHeaders:
modulename: "github.com/XciD/traefik-plugin-rewrite-headers"
version: "v0.0.2"
Dynamic config:
http:
routes:
my-router:
rule: "Host(`localhost`)"
service: "my-service"
middlewares :
- "rewriteHeaders"
services:
my-service:
loadBalancer:
servers:
- url: "http://127.0.0.1"
middlewares:
rewriteHeaders:
plugin:
rewriteHeaders:
header: "Location"
regex: "^http://(.+)$"
replacement: "https://$1"
Disclaimer: I'm the author of the plugin
I have following Zuul configuration. Also I have disabled Eureka since I have service discovery in place.
server:
port: 7777
ribbon:
eureka:
enabled: false
zuul:
prefix: /api
routes:
yourService:
path: /newpath/**
serviceId: yourService
yourService:
ribbon:
listOfServers: localhost:8080/rest
Now when I hit localhost:7777/api/newpath Zuul does a 302 redirection rather than reverse-proxying transparently. Please advise how to stop this redirection and get Zuul to reverse-proxy transparently.
Try it with trailing slash as it's in the rule:
http://localhost:7777/api/newpath/