[Seaside] Kom listening to loopback interface only

Boris Popov boris at deepcovelabs.com
Sun Aug 24 22:19:29 UTC 2008

When listening on localhost only no other network device would be able to access the service, regardless of what happens to your network configuration in the future. It is a key requirement in certain compliance environments.


-Boris (via BlackBerry)


From: seaside-bounces at lists.squeakfoundation.org 
To: Seaside - general discussion 
Sent: Sun Aug 24 15:16:49 2008
Subject: Re: [Seaside] Kom listening to loopback interface only 

Avi Bryant wrote: 

	On Sun, Aug 24, 2008 at 7:46 AM, Giovanni Corriga <giovanni at corriga.net> <mailto:giovanni at corriga.net>  wrote:

		Hi all,
		I was going over the bugs for KomHttpServer on bugs.squeak.org and I
		am a little undecided about bug #6738
		(http://bugs.squeak.org/view.php?id=6738). What do you think about an
		option to make Kom listen only to the loopback interface
		Would that be useful to you?

	Yes - it's something we modify Kom to do anyway, so an option would be great.

Hmm, this is curious.  I've never needed to do it.

In contrast, I have Apache listening to the world on port 80, and Seaside/Comanche listening on a high port, and Apache redirecting to the high port.  And the high port is firewall blocked and thus only local processes (i.e., Apache) can send to it.

Doesn't that achieve the same thing?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080824/f4410fe0/attachment.htm

More information about the seaside mailing list