#3926 regression: Self-signed certificates
See original GitHub issueDescribe the bug
See previously documented bug: #3341
For those of us behind a corporate proxy with self-signed certificates, we need a way to configure that.
With the built-in yarn
, there’s no clear way to do that.
Reverting to v3.1.1 works.
Expected behavior autorest should function behind a proxy.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
What is a Self-Signed Certificate? Advantages, Risks ...
Self -signed certificates offer some advantages when used in internal networks and software development phases, however, they can also create ...
Read more >Does Self-signed certificate differ from CA from a security point ...
When looking at functionality alone, a self-signed certificate offers neither more or less security then one issued from a leading certificate authority.
Read more >North Carolina Bar Examiners
The public may attend the hearing and may sign up to offer comments. ... self-funded occupational licensing board that grants certificates of qualification ......
Read more >bonifay rodeo
7,115 likes · 25 talking about this · 3,926 were here. ... Sign up for the newsletter to receive weekly updates for rodeos...
Read more >Local Testing Using Self-Signed Certificates - BrowserStack
Self -signed certificates are digital certificates for websites which are not signed by a publicly-trusted certificate authority (CA). Given the CA in such ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Alternativel would be to remove the
--no-default-rc
to still use the global yarn config but useYARN_IGNORE_PATH=1
instead to prevent a different version of yarn from being loaded(Issue solved in #3926)Could do this at least as a short term solution.
The suggestion in #3341 to install yarn separately worked for me, then I was able to issue the command
yarn config set strict-ssl false -g
to fix this error message: