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.

Sign up for GitHub

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

Jump to bottom

Investigate and fix failure to handle 308 Moved permanently for registry responses #264

Closed

coollog opened this issue May 9, 2018 · 1 comment

Assignees

Labels

Contributor

coollog commented May 9, 2018

No description provided.

coollog added the priority: p1 label

Contributor Author

coollog commented Jun 11, 2018

This should be taken care of in the fix for #388.

coollog mentioned this issue

Handles 301 and 308 redirects for registry responses. #408

Merged

coollog self-assigned this

coollog closed this as completed in #408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment