Weekend meme-making-marathon with my kids, and here is the best one. If we had been able to find our Playskool Han, it would’ve been a Han Trio!
You recognize those logos up there, don’t you?
The favicon (Favorite icon), shortcut icon, Web site icon, tab icon or bookmark icon is nothing new. It’s been around for well over a decade now. There are tons of articles and sites out there to help you make a favicon and upload it to your site.
And yet, so many sites – mostly blogs – don’t have one. Why not?
Seriously, with how easy it is to do, the only reason I can think of that your site would not have a favicon is because you don’t know why you should have a favicon.
So, here are the reasons your site
should must needs to have a favicon.
If you are a Kindle user – the tablet or the app – Amazon has a great (free) service that allows you to select files on your computer – PC or Mac – and send them to your Kindle (or registered Kindle app) using the Kindle native format. This is great for when the file you want to send is too large for email attachment restrictions – corporate or otherwise – and you can’t use their email service.
But if you are just installing the application, and trying to register it behind a corporate proxy, you might run into the same problem I did: the dreaded and ubiquitous “Network error occurred”!
A few colleagues and I recently started Mercenary as an open source project. One of the first problems we faced was accessing our GitHub repository when we were behind the corporate proxy.
I resolved this by installing and configuring Cntlm on my Windows workstation, as I described in my previous post.
Next, I updated my Git configuration file (usually located at %UserProfile%\.gitconfig) and added the following lines:
[http] proxy = http://localhost:3128 [https] proxy = http://localhost:3128
I restarted my Git client and problem solved!
Cntml is easy to install and configure, and supports multiple platforms. This post, on the other hand, is specific to Windows. For more information on using Cntlm on a different platform, consult their official wiki.
What Proxy Problems?
Corporate proxy server are a pain. If you don’t know why, you haven’t been working in a corporate environment very long.
- The proxy server ignores your Windows host file
- Most 3rd party Windows applications don’t support NTLM natively
- For those that do, they usually store your credentials in plain text (bad)
- And whether they do or not, when your credentials change (i.e., regularly scheduled forced password changes) you now have multiple places to update your credentials
While some of these are specific to being a software developer, most of these will impact you at some point in time. All of these problems drove me to look for a solution – or in some cases, a better solution than whatever hack I was using.
Enter Cntlm, “…an NTLM / NTLM Session Response / NTLMv2 authenticating HTTP proxy… It stands between your applications and the corporate proxy, adding NTLM authentication on-the-fly.” – from the Cntlm homepage.