Unauthorised error not redirecting for the first time in oathkeeper

[vsumit89]

I am encountering a unauthorised error in oathkeeper.
In my application when I logout and again try to hit the protected URL, for the first time it throws Access Credentials are Invalid error and then does not redirect to the login page even when I have a handler for unauthorised error. But when I reload the page again it throws the same error but this time it redirects to the login page.
These are my oathkeeper rules.

handlers:
    redirect:
      enabled: true
      config:
        to: http://127.0.0.1:4455/.factly/kavach/web/auth/login
        when:
          -
            error:
              - unauthorized
              - forbidden
            request:
              header:
                accept:
                  - text/html
    json:
      enabled: true
      config:
        verbose: true

[vinckr]

Check out our Oathkeeper examples, maybe those can be of help. If they don't help let me know.

[vsumit89]

Hey @vinckr, I went through the examples and I have exactly the same implementation but it doesn't work the way it should.
This is for reference from oathkeeper examples -

handlers:
    redirect:
      enabled: true
      config:
        to: http://127.0.0.1:4455/login
        when:
          - error:
              - unauthorized
              - forbidden
            request:
              header:
                accept:
                  - text/html

When I logout from the application and hit a protected URL without having the cookie_session, instead of throwing unauthorized error and redirecting to the login page, oathkeeper lets it pass through for the first time, but when I reload it, it redirects.
This is the protected URL - http://127.0.0.1:4455/.factly/dega/studio/<.*>
This is the URL to which I am redirecting - http://127.0.0.1:4455/.factly/kavach/web/auth/login

[Intevel]

Hey @vsumit89! Did you fixed this?

[vsumit89]

@Intevel No I wasn't able to.

[fswu0831]

Hi @Intevel @vsumit89
I'm confronting same issue. Dis you fixed this?
I tried to use Oathkeeper v0.40.8 and v0.39.4

[Intevel]

Nope