blog.majcica.com
Open in
urlscan Pro
2a01:238:20a:202:1159::
Public Scan
URL:
http://blog.majcica.com/2016/01/13/tough-life-behind-a-proxy/
Submission: On October 03 via manual from US — Scanned from DE
Submission: On October 03 via manual from US — Scanned from DE
Form analysis
2 forms found in the DOMPOST http://blog.majcica.com/wp-comments-post.php
<form action="http://blog.majcica.com/wp-comments-post.php" method="post" id="commentform" class="comment-form">
<p class="comment-notes"><span id="email-notes">Your email address will not be published.</span> <span class="required-field-message" aria-hidden="true">Required fields are marked <span class="required" aria-hidden="true">*</span></span></p>
<p class="comment-form-comment"><label for="comment">Comment <span class="required" aria-hidden="true">*</span></label> <textarea id="comment" name="comment" cols="45" rows="8" maxlength="15360" required="" minlength="15"></textarea></p>
<p class="comment-form-author"><label for="author">Name <span class="required" aria-hidden="true">*</span></label> <input id="author" name="author" type="text" value="" size="30" maxlength="245" required=""></p>
<p class="comment-form-email"><label for="email">Email <span class="required" aria-hidden="true">*</span></label> <input id="email" name="email" type="email" value="" size="30" maxlength="100" aria-describedby="email-notes" required=""></p>
<p class="comment-form-url"><label for="url">Website</label> <input id="url" name="url" type="url" value="" size="30" maxlength="200"></p>
<p class="comment-form-cookies-consent"><input id="wp-comment-cookies-consent" name="wp-comment-cookies-consent" type="checkbox" value="yes"> <label for="wp-comment-cookies-consent">Save my name, email, and website in this browser for the next time
I comment.</label></p>
<p class="form-submit"><input name="submit" type="submit" id="submit" class="submit" value="Post Comment"> <input type="hidden" name="comment_post_ID" value="758" id="comment_post_ID">
<input type="hidden" name="comment_parent" id="comment_parent" value="0">
</p>
<noscript><input type="hidden" name="JS04X7" value="NS1"></noscript>
<noscript>
<p><strong>Currently you have JavaScript disabled. In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page.</strong>
<a href="http://enable-javascript.com/" rel="nofollow external">Click here for instructions on how to enable JavaScript in your browser.</a></p>
</noscript>
</form>
GET http://blog.majcica.com/
<form role="search" method="get" class="search-form" action="http://blog.majcica.com/">
<label>
<span class="screen-reader-text">Search for:</span>
<input type="search" class="search-field" placeholder="Search …" value="" name="s">
</label>
<input type="submit" class="search-submit" value="Search">
</form>
Text Content
Skip to content MUMMY'S BLOG AS MOTHER MADE IT – MARIO MAJČICA'S WEB LOG * About Mario Majčica * Contact Me TOUGH LIFE BEHIND A PROXY In many enterprises when it comes to Internet access you will find yourself behind a proxy server. In such conditions many application do require a specific setup or they will not work at all. Recently I had to install a npm package from the official public npm repository and the “usual” command doesn’t work. Thus in case of npm client behind a proxy server, you need to pass the following argument --proxy. My command from: npm install -g tfx-cli became npm --proxy http://my.proxy.com:8080 install -g tfx-cli Also, as I am actively using Visual Studio Code, I had an unpleasant surprise. If you do tend to install a Visual Studio Code extension (plugin) and you are behind a proxy, at the moment you are doomed. There is no way, in the latest version at the time of writing, to install Visual Studio Code extension if behind a proxy. When it comes to .NET software development, all of the commonly used classes as HttpClient do cope well with proxy, the only problems is that developers rarely think about it and do not implement adequate support. In this particular case specifying a proxy in HttpClientHandler is the solution, which then needs to be passed to the HttpClient constructor. So fellow developers please have mercy for all of the people behind a proxy, it ain’t an easy life! TwitterLinkedInFacebookWhatsAppShare Tagged as: HttpClient, HttpClientHandler, npm, proxy, Visual Studio Code Categorized in: Articles, Development, Uncategorized January 13, 2016 Mario Majcica2 Comments POST NAVIGATION TFS 2015 Build Agent failing syncing the repository PowerShell tips and tricks – Multipart/form-data requests 2 THOUGHTS ON “TOUGH LIFE BEHIND A PROXY” 1. Pingback: TFS 2015 behind a proxy – Mummy's blog 2. Pingback: Visual Studio Code behind a proxy – Mummy's blog LEAVE A REPLY CANCEL REPLY Your email address will not be published. Required fields are marked * Comment * Name * Email * Website Save my name, email, and website in this browser for the next time I comment. Currently you have JavaScript disabled. In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page. Click here for instructions on how to enable JavaScript in your browser. © 2015 Mario Majčica All Rights Reserved Decode Theme by Macho Themes Search for: RECENT POSTS * Signing Git Commits * Building Visual Studio projects with DevEnv.com * Starting a TFS release via REST API * Azure DevOps extension for XL Deploy * Download a file with TypeScript * Node10 provider available for Agent v2.144.0 * Uploading XL Deploy DAR package via TypeScript * Living Documentation and test reports in VSTS/TFS pipelines * Deploy SSIS packages from TFS/VSTS Build/Release * Provisioning WebDeploy in VSTS/TFS release via DSC script * Using global application host file in Visual Studio 2015+ * Get Users SID with PowerShell * Joining strings in pipeline * Automate setting ‘Retain indefinitely’ flag on your releases * Uploading build/release tasks to VSTS * Managing VSTS/TFS Release Definition Variables from PowerShell * Using Windows Machine File Copy (WinRM) VSTS extension * (no title) * Persisting sensitive information with PowerShell * TextTransform issues after VS Project Upgrade * XL Deploy in VSTS/TFS build/release pipelines * Using Git with self-signed certificate at the user level * VSTS/TFS Agents behind a proxy * TFS Tips from the Trenches * Working with TFS in IntelliJ IDEA via VSTS Plugin CATEGORIES * .NET (19) * ASP.NET (6) * C# (14) * DevExpress (3) * Moq (1) * MSTest (2) * TPL (1) * WCF (2) * Articles (15) * Azure DevOps (4) * Best Practice (12) * Cisco (1) * IOS (1) * CodedUI (5) * Cryptography (4) * Development (4) * SQL (2) * Git (2) * Hardware (1) * IIS (2) * IntelliJ IDEA (1) * JavaScript (1) * Networking (1) * News (1) * Nexus (3) * NodeJs (2) * PowerShell (13) * Security (9) * SonarQube (3) * SpecFlow (2) * Testing (5) * TFS (29) * TFS 2015 (12) * TFS 2017 (4) * Tips and Tricks (2) * TypeScript (3) * Uncategorized (42) * Unit test (4) * Visual Studio (12) * Nuget (2) * Templates (1) * VSIX (3) * VSTS (9) * Windows 8 (1) * WiX (1) * XebiaLabs (7) * XL Deploy (5) * XL TestView (2) META * Log in * Entries feed * Comments feed * WordPress.org ✓ Thanks for sharing! AddToAny More…