-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too many redirects #165
Comments
@vpavlin do you have any hunch on this? |
It's gonna be connected to how we deal with cookies, but no, not yet...looking in to it now |
Blocked by #174 - cannot be properly debuged at the moment |
I think the whole problem is also browser related. It seems in particular Chrome where this error comes up. I don't think I have seen it in another browser yet. |
I also faced this today |
I am facing this problem since yesterday. |
Saw this even in firefox |
got this
I think it is a problem with implementation. It keeps redirecting to auth even if logged in. Should be fixable. Don't think it is intermittent anymore. I see it everytime these days. |
Doesn't seems to create any problems on prod. So this can be done later |
Ok. I see this happening even on prod and it is quite frequent |
After #250 this issue is not seen. I will still hang to this for a while before closing this |
Saw this on my local machine This might be the reason
|
@sthaha @kishansagathiya - So this is all 🍪 magic! There are 2 facets to this problem.
The whole cookie story is messed up for So, even though cookies are set at fabric8-jenkins-proxy/internal/proxy/proxy.go Line 275 in f86d376
fabric8-jenkins-proxy/internal/proxy/proxy.go Line 293 in f86d376
needsAuth remains true and fabric8-jenkins-proxy/internal/proxy/proxy.go Lines 377 to 381 in f86d376
To fix this, we need to make 2 changes.
Once this is fixed, you will encounter the next problem. Read on 🤷♂️
The cookies will now be set for fabric8-jenkins-proxy/internal/proxy/proxy.go Lines 299 to 308 in f86d376
cacheKey remains empty and we get fabric8-jenkins-proxy/internal/proxy/proxy.go Lines 369 to 371 in f86d376
fabric8-jenkins-proxy/internal/proxy/proxy.go Lines 377 to 381 in f86d376
And hence we go in circles! This second problem was staring us in the face with #174, but 🤷♂️! The fix for local development definitely lies in generating local certificates, or something of the like. But will this fix the |
What you describe makes perfect sense for local development, but does not at all explain the stage/prod issue as none of 2 causes you mentioned are present when running in prod/prev clusters. Also, during debugging this, I saw that cookies seemed to be set properly. I still think this is connected to how proxy handles cookies, but I am pretty sure neither |
Proxy often gets into redirect loop which results in too many redirects error - after showing this error, browser redirects to the Jenkins successfully.
The issue probably lies in how we work with cookies and generally verify if user is logged in
The text was updated successfully, but these errors were encountered: