Skip to content
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

error parsing HTTP 400 response body: #4

Open
DrPreobrazhensky opened this issue May 24, 2018 · 4 comments
Open

error parsing HTTP 400 response body: #4

DrPreobrazhensky opened this issue May 24, 2018 · 4 comments

Comments

@DrPreobrazhensky
Copy link

Thank for sharing aws-ecr-http-proxy.

When I do docker push an error occurred.

error parsing HTTP 400 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>\r\n<body bgcolor=\"white\">\r\n<center><h1>400 Bad Request</h1></center>\r\n<center>The plain HTTP request was sent to HTTPS port</center>\r\n<hr><center>openresty/1.13.6.1</center>\r\n</body>\r\n</html>\r\n"
@mqasimsarfraz
Copy link
Collaborator

hi @DrPreobrazhensky. thanks for trying the proxy.

Are you able to pull images? Also it would be great if you post your configuration (docker_proxy_backend format and docker_proxy_backend_schema) and nginx logs here.

@DrPreobrazhensky
Copy link
Author

Yes I able to pull.
I've switched already from aws-ecr-http-proxy to nginx and own config but my server_name like name.subdomain.domain.net and other settings is default.

Sorry I can't provide more info. I guess we can close this issue.

@mqasimsarfraz
Copy link
Collaborator

That is strange. Have you marked the proxy insecure? or SSL/TLS termination? or any other modifications?

@varunpalekar
Copy link

I am also getting something similar on docker push.

Authentication: IAM Role
Version: 1.4.0

Command: docker push aws-registry-proxy-test.example.com/abc:master
Error:

The push refers to repository [aws-registry-proxy-test.example.com/abc:master]
d52a5eca0207: Preparing
6d1e6cb4df22: Preparing
0029f0c4cc17: Preparing
2b93c8d2bde6: Preparing
b20016f37d0d: Preparing
76a2a461089b: Waiting
denied: User: arn:aws:sts::<acount-id>:assumed-role/ecr-proxy/<role> is not authorized to perform: ecr:InitiateLayerUpload on resource: arn:aws:ecr:eu-west-1:<account-id>:repository/abc

Can we somehow separately handle the 401 and 403 requests also like 3xx?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@varunpalekar @mqasimsarfraz @DrPreobrazhensky