Autorest does not work behinde Corporate Proxy
See original GitHub issueAfter installing Autorest npm install -g autorest
when i use autorest command line it can’t download file because i am using my corporate proxy the configuration is set on npm but autorest does not work with the same configuration of my npm proxy
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (6 by maintainers)
Top Results From Across the Web
How to configure proxies for the Azure SDK for Python
Set in Python code. You can set proxy settings using environment variables, with no custom configuration necessary. Python Copy.
Read more >Swashbuckle using port 80 for https when run behind reverse ...
Doing this, any URL generation in the app (behind reverse proxy) should respect the port-forwarding value. According to documentation known ...
Read more >PowerShell + AutoRest + Swagger = Instant Modules by Adam ...
With AutoRest, you can generate easy-to-use PowerShell cmdlets ... Finally, they'll be aware of some of the issues to watch out for and...
Read more >Swashbuckle.AspNetCore - Discover .NET
json ). This won't work if your app is hosted on an IIS virtual directory or behind a proxy that trims the request...
Read more >Provider responds with "409 Conflict" and errors with ...
Problem. While deploying Terraform configuration to create a PostgreSQL Database, PostgreSQL Server, and AzureRM Storage Account, the following ...
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
I know that you have closed this issue but I also sit behind a corporate firewall…and am haiving a nightmare with this. I can successfully pull down the latest autorest version using the npm configs for proxies, However when I attempt to try and generate a client using autorest it tries to pull down the dependancies and fails i.e. packages autorest.csharp and autorest.core etc. and fails with incorrect framework versions. also It seems to be using Yarn somewhere to get these dependent packages listed above. Any pointers would be great
@fearthecowboy Via NPM this works fine now, so feel free to close this issue.