While working on an ASP.Net project at work, I found a strange “feature” (I’m more inclined to call it an annoyance) that is built into certain browsers. It seems that Firefox and WebKit have automatic port blocking built into them for specific ports. I was specifically trying to use port 6000 (a seemingly random, easy to remember port) but couldn’t access the web server. After a little searching, I managed to find some information and thought I’d share it.
Read the rest of this entry »About the Author
Hey there! My name is Richard Marskell and I'm the co-founder of LBC IT Solutions, Inc.. I've been developing websites, apps and even games for over 20 years.
I previously worked at a leading Canadian market research company for 8.5 years, managing their tech team and projects—everything from project & resource management to designing client websites.
This blog is where I share some of the things I've found (or figured out) throughout my career.
Have something to say? Drop me a comment or tweet me .
Latest Posts
- » Excel Tip: Helpful Keyboard Shortcuts
- » Windows 10 Announced - New Features Abound
- » Enable or Disable Torrent / P2P Traffic in IPFire
- » Remotely List and Disconnect Users in Windows
- » Git + Stash: Set up Self-Signed SSL Certificate in Windows
- » SourceTree: Fix for Slow Operation on Windows
- » Using Integers as Boolean Flags
- » 2014 Update
- » How to fix: File in Use - Personal.xlsb is locked for editing
- » Browser Automatically Blocks Ports
Post Calendar
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | ||