[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] limiting connections
- Subject: Re: [cobalt-users] limiting connections
- From: flash22@xxxxxxx
- Date: Thu Oct 4 17:11:42 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Wed,3 Oct 2001, Carrie Bartkowiak wrote two really really long sentences:
> I was just downloading all of the updates/patches to my home machine
for archival purposes, and the Sun site would only allow me
to have 2 downloads going at once.
> How can I do the same thing on my servers for both FTP and HTTP?
Sometimes I see a person in netstat with 20 connections to a particular
site - no idea why, but that bugs me.
"Greedy" comes to mind.
I'd like to limit that if I can.
..
For ftp it's easy, just add
MaxClientsPerHost 2
To proftp.conf, this will limit total connections per IP to 2....caveat,
if your customers have a habit of crashing out of ftp without quitting,
they won't be able to connect after 2 connects untill they wait 15-30
minutes for the hung connections to time out, 2 might be small , depends
on your customers ;)
http is harder, and you probably shouldn't try, the reason some clients
show so many connections is they have probably been forced back to HTTP
1.0, which doesn't do keep-alive, so the browser opens a new connection
for every object on a web page. (every image, etc)
The probleem is, if you
refuse the connections after some point, those objects won't get loaded,
the browser really has no way of knowing that "you can't have it" means
"You could have it later if you asked again", browsers aren't very good
at etiquitte and protocol -/
gsh