Github container registry (ghcr.io) does not handle multiple scopes in a token request correctly

[molian6]

Select Topic Area

Bug

Body

Hi, I'm using containerd to push images to ghcr.io, because of some redirection reasons, multiple scopes are added to the token request. However ghcr.io does not ignore the invalid scope, it seems it's only picking the first scope, and returning 403 on the token request if the first scope is not a valid ghcr.io scope.

curl -v https://ghcr.io/token\?scope\=repository%3Agithub-username%2Fimage-path%3Apull\&scope=repository%3Asome-random-registry%3Apull working

curl -v https://ghcr.io/token\?scope\=scope=repository%3Asome-random-registry%3Apull\&repository%3Agithub-username%2Fimage-path%3Apull not working, returning 403

The difference is in the first request, I put the github container registry scope as the first scope. And in the second request, I put the I put the github container registry scope as the second scope.

I believe the correct behavior should be ignoring the invalid scope, and return 200 as long as there's one scope valid.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐