docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
232 stars 40 forks source link

index.docker.io loads Docker Hub without redirection with non-working reCAPTCHA #2280

Open rimelek opened 1 year ago

rimelek commented 1 year ago

Problem description

It is possible to open index.docker.io from a webbrowser and the website does not redirect to hub.docker.com so when people visit the site, they see an error message:

ERROR for site owner: Invalid domain for site key

It was mentioned in an old topic on the Docker forum, but there were no answers. Two days ago we got a new report and I could confirm the issue. I don't know if the index site should have a valid key or not, but I think, even if it is a bug, users should be redirected to hub.docker.com to avoid confusion.

Debug Information

Browser name and version: From any browser, but I have Google Chrome Version 107.0.5304.87 (Official Build) (arm64)

URL: https://index.docker.io

Timetamp or time range: Sun Oct 30 22:33:47 CET 2022

Error messages (on screen or in browser console)

ERROR for site owner: Invalid domain for site key

Although the problem is not the error message, but the fact that Docker Hub works on two different domains without redirecting the user to the working site in a web broeser.

Task List

ingshtrom commented 1 year ago

Thank you for the report! This brings up a long-standing issue with our domains which re-ignited an old conversation, internally. Thank you for that, as well. 🎉

We agree this behavior is incorrect and confusing. We do not have a timeline for a fix, but we are planning to implement a redirect so that only hub.docker.com can serve the Docker Hub website. 😄

Thank you again. Have a Majestic Monday!

ingshtrom commented 1 year ago

We have released the fix for this. Please re-open the ticket if you see the same problem or open a new ticket if you see any new issues. Thank you for the report!

rimelek commented 1 year ago

@ingshtrom We got a new report on the Docker forum about the same issue. I checked it and the redirection doesn't work. It looks like I can't reopen the issue or I don't know how.

ingshtrom commented 1 year ago

I will re-open the issue. I am sorry last week was crazy and I forgot to comment on this thread. The redirects were put in place and then caused a production issue, so we needed to roll them back.

Can you link to forum postings with this confusion? That would help with some internal discussions surrounding retiring these old domains in the long term.

In the short term, I'm not sure how we can solve this redirect issue without further issues, unfortunately. We are open to ideas, though.

rimelek commented 1 year ago

Can you link to forum postings with this confusion?

Oh.. I am sorry, I wanted to include it in the original post, but I forgot about it. Now I added it to the original post so you can find it more easily. I leave the link here too: https://forums.docker.com/t/broken-recaptcha-on-docker-hub/99889

We are open to ideas, though.

When I have an idea, I will let you know. Until then I will ask everyone to use the hub.docker.com domain as I have always done it.

rimelek commented 1 year ago

@ingshtrom I have been thinking and I have some ideas.

  1. Wouldn't a javascript or html-based redirection help? Something like this:

    <meta http-equiv="refresh" content="0;URL='https://hub.docker.com'" /> 

    It would be added to the header only when the domain name is not hub.docker.com.

  2. An other idea is changing the ontent of the site when the domain is not hub.docker.com Intstead of the original content, you could show a nice button (link) to the hub with a note saying that the visitors should use the new domain.

  3. You could also use the two solutions together and redirect automatically with that meta tag if the visitor doesn't click on the link in 10 seconds.

  4. MinIO has an other solution. They use it to redirect between ports, not domains. I guess they detect the user-agent, but I am not sure. When you open the MinIO API URL from a webbrowser, it redirects to the MinIO Console's port (web interface). That shouldn't affect docker login

thaJeztah commented 1 year ago

Some more details about the history behind the index.docker.io domain (and why it's still shown in various places) can be found in https://github.com/docker/cli/issues/3793#issuecomment-1269051403

ingshtrom commented 1 year ago

@rimelek I am sorry for the delay. We are having ongoing internal discussions about a larger issue related to this ticket. I will keep this updated. Your ideas and input are helpful. Thank you!