I am running a Kubernetes Cluster with an Nginx-ingress fronting couple of web apps. Because Nginx doesn't support SSO/OIDC by default, I use an oauth_proxy for authentication.

In detail I use oauth2_proxy (https://github.com/pusher/oauth2_proxy) with Azure AD.

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-ingress-internal
  namespace: ingress-nginx
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/auth-url: "https://example.com/oauth2/auth"
    nginx.ingress.kubernetes.io/auth-signin: "https://example.com/oauth2/start?rd=$escaped_request_uri"
    nginx.ingress.kubernetes.io/auth-response-headers: "authorization, x-auth-request-user, x-auth-request-email, x_auth_request_access_token"

spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /home(/|$)(.*)
        backend:
          serviceName: app-homepage-frontend-service
          servicePort: 80
      - path: /homepage-backend(/|$)(.*)
        backend:
          serviceName: app-homepage-backend-service
          servicePort: 80

I skiped some details like tls. So in general everything is working, only verified users are able to access the web pages.

The issue is that my frontend is writte in Angular which use hash-routing. And if try to enter a deep route like

https://example.com/home/#/page1/subpage2

just base path (/home) is passed as redirect url. So when I'm authorized successfully, I get redirected to https://example.com/home.

Is there any veriable instead of $escaped_request_uri, which pass the whole url?