Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

At work, we've got Windows Server 2008 running. I've set up XAMPP, and a few websites - everything works perfectly.

However, outgoing port 80 is blocked in the firewall for 'security' reasons. I was wondering if there's any merit to this?

share|improve this question
1  
The firewall in the server? Or the firewall in a spearate box that shields your company's network from the internet? – Andrew Turner Dec 20 '11 at 20:47
1  
Sounds like typical behavior from Windows. Block outgoing HTTP, IT'S DANGEROUS!! (end sarcasm) – Tim Dec 20 '11 at 21:55
    
Tim, after you have had your corporate machines turned into a 'bot network and had to deal with the consequences you'll learn the value of egress filtering and not say anything that daft again. – JdeBP Dec 23 '11 at 17:14

Well, from a security standpoint, every port should be closed by default. And then if there is need,the necessary port can be opened. Port 80 isn't or shouldn't be an exception.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .