You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2024. It is now read-only.
With the latest versión, when you use a registry that uses basic authentication, I receive the next error: [4/19/2020] [8:03:15 PM] [Express ] › ⚠ warning Error: getaddrinfo ENOTFOUND USER User:443
For <registry_user> you see the real user name. After doing some research, right now the basic auth is doing by concatenating the user:pass inside the calling URL. Despite this could work, the restler parser is failing and takes the user as FQDN for the DNS.
My recommendation is to change how the options of restler are being generated and use the username and password parameters. Something like:
Hi, @jc21@jamesdube@huapox. Are you open to allowing more contributors to the project? Many requests, issues and PRs are open without an answer for a long time, and I think it's a shame because the solution is quite good, I'd say, to abandon it. What do you think?
With the latest versión, when you use a registry that uses basic authentication, I receive the next error:
[4/19/2020] [8:03:15 PM] [Express ] › ⚠ warning Error: getaddrinfo ENOTFOUND USER User:443
For <registry_user> you see the real user name. After doing some research, right now the basic auth is doing by concatenating the user:pass inside the calling URL. Despite this could work, the restler parser is failing and takes the user as FQDN for the DNS.
My recommendation is to change how the options of restler are being generated and use the username and password parameters. Something like:
I tried to debug the solution but it fails with the table-ui so I cannot send you a pull request. Thanks!
The text was updated successfully, but these errors were encountered: