Re: HTTP::Daemon Security Question

Questions like these confuse me. Why are you not using Apache? Seems to me you could easily solve your problems by just using Apache and configuring it accordingly:

Order deny,allow
Deny from all
Allow from 127.0.0.1
[download]

Am i missing something? :/

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Comment on Re: HTTP::Daemon Security Question Download Code

Replies are listed 'Best First'.
Re^2: HTTP::Daemon Security Question by bkiahg (Pilgrim) on Jan 06, 2009 at 19:57 UTC
I've never used Apache and I needed a lightweight front end for my applications. This was the simplest form I could find and if I can get it to not accept outside connections it will be perfect for what I need. How large is Apache? The smaller the install file the better. How hard is it to configure correctly? If I recall correctly Apache is a great program, but it has a steep learning curve to properly set up. How well does it perform on windows? Never heard of anyone running it on a regular windows box (xp, 2000). Maybe its very common, just never had any personal experience with it. So in summation, I am using this because: I love perl and will always opt for an all perl solution! In 19 lines of code I have found a perfect solution to what I was looking to do. I am ignorant on the procedures of Apache Too lazy to educate myself for this particular project.. lol. So if there is a strong reason that I am unaware of that I should be using Apache, please let me know. I want to do this correctly, but am unaware of what I am unaware of.	[reply]
Re^3: HTTP::Daemon Security Question by jeffa (Bishop) on Jan 06, 2009 at 20:13 UTC
"So if there is a strong reason that I am unaware of that I should be using Apache, please let me know." Because it has already been written, tested, standardized, industry approved and backed. It runs just fine on Windows, but I have yet to find a compelling reason to not use Linux for this type of application. Linux and Apache got the market first -- Microsoft is too busy figuring how to control their users for me to consider paying for their product. Apache is free. Linux servers are cheap. I too love Perl, but if I am writing a web application -- and that's pretty much all i do these days -- i am going to use Apache to handle what your 19 lines does. Sure, it's bigger -- but once you learn how to use it you can apply that knowledge to many more existing web applications written by a vast array of scruffy hackers. Use the right tool for the right job. And if your 19 lines is the right tool then there you have it. Just realize you didn't need to even write those 19 lines. Apache does all of that. And thanks to packages like xampp installation and configuration just gets easier and better. jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply]
Re^4: HTTP::Daemon Security Question by bkiahg (Pilgrim) on Jan 06, 2009 at 20:43 UTC
Thank you. I will check out xampp. I've always been interested in Apache, but like I said always heard there was a steep learning curve to do correctly. Also unfortunately all of my clients run on windows based systems, so no Linux for me...	[reply]