https://issues.joomla.org/tracker/joomla-cms/11064 is redirecting to the homepage for me...
But i have noticed something similiar in the past.
works for me.
All issues are currently redirecting me to the home page. Of course having said that the link above works just fine. But all the footer links are not (e.g. https://issues.joomla.org/tracker/joomla-cms/11534). I go to oAuth login everytime with the link https://github.com/login/oauth/authorize?client_id=e7208079bca517f781dd&redirect_uri=https%3A%2F%2Fissues.joomla.org%2Flogin%3Fusr_redirect%3DaHR0cHM6Ly9pc3N1ZXMuam9vbWxhLm9yZy90cmFja2VyL2pvb21sYS1jbXMvMTE1MzQ%3D&scope=public_repo
I think this is related to #863 - I couldn't access that url inside github and eventually ended up at the point where github reauthorized me. I eventually worked around the issue by directly editing the issue (which url did work) and finally i got redirected back to the issue....
Also now I have (finally) visited that page. The original URL from the footer links now actually do work. So I guess once that page has been successfully navigated to once (in my case once I saved the edit) it's now 'fixed' in some way?
When this happens to me (almost every day for the last few weeks) as soon as I open chrome console and try to record the network traffic it starts to work
I've just sent a screen recording to michael. can't post it in here because of the restrictions on file types you can upload :(
For me only using Firefox instead of Webkit based browser (like chrome) works..
I got the same problem on vivaldi (webkit/blink), with firefox it works.
Redirects:
https://issues.joomla.org/tracker/joomla-cms/11803 -> https://github.com/login/oauth/authorize -> https://issues.joomla.org/login?code=-removed-&usr_redirect=aHR0cHM6Ly9pc3N1ZXMuam9vbWxhLm9yZy90cmFja2VyL2pvb21sYS1jbXMvMTE4MDM%3D -> https://issues.joomla.org/
Well that's the correct redirect chain (OAuth request to GitHub, GitHub sends it back to our login handler, and we redirect you to whatever page was requested). Why it's not reading that usr_redirect
parameter correctly is interesting though; you should be ending up on that issue you requested, not the homepage.
Thats what we've been saying
On 26 August 2016 at 13:38, Michael Babker notifications@github.com wrote:
Well that's the correct redirect chain (OAuth request to GitHub, GitHub
sends it back to our login handler, and we redirect you to whatever page
was requested). Why it's not reading that usr_redirect parameter
correctly is interesting though; you should be ending up on that issue you
requested, not the homepage.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#865 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPH8dK9T2rqFrnYiYNG6oiPWxBHZLJNks5qjt5JgaJpZM4Jjrs_
.
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
http://brian.teeman.net/
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-24 10:59:20 |
Closed_By | ⇒ | wilsonge |
works for me.