Posts Tagged ‘403’

Besides routing and redirecting you can serve static responses with Envoy. In this case I want to serve a forbidden response (403) route_config:   virtual_hosts:   – name: picockpit     domains: [“picockpit.local:443”, “picockpit.local”]     routes:       – match: { prefix: “/demo” }         direct_response:           status: 403           body:             inline_string: “Forbidden.”        – match: {prefix: “/”}         route: {cluster: target_picockpit} It can also serve…