Subj : Webv4 set limit per each
To   : plt
From : Digital Man
Date : Sun Aug 29 2021 14:11:58

  Re: Webv4 set limit per each
  By: plt to MRO on Sun Aug 29 2021 04:33 pm

 > -=> MRO wrote to plt <=-
 >
 >  MR>   Re: Webv4 set limit per each ip address
 >  MR>   By: plt to Digital Man on Sun Aug 29 2021 12:55 pm
 >
 >  >   Re: Webv4 set limit per each ip address
 >  >   By: Digital Man to plt on Sun Aug 29 2021 02:54:47
 >
 >  >  >   Re: Webv4 set limit per each ip address
 >  >  >   By: plt to All on Sat Aug 28 2021 12:51 am
 >
 >  >  >  > Hello
 >
 >  >  >  > Is there a option to limit the max connections for webv4 that is
 >
 >  >  >  > using
 >  >  >  > the same ip address?
 >
 >  >  > The web server does not have that feature, no.
 >
 >  > Is that a possible option that can be added?
 >
 >  MR> why would you want to do that? do you know whats happening?
 >  MR> if you limited connections it would load even slower for the clients.
 >
 >  MR> leave it alone and let it run.
 >
 > How so, Synchronet bbs already use ip.can.

The ip.can has nothing to do with the maximum concurrent connection limits supported some of the Synchronet server (FTP, mail, terminal). Web browsers *normally* open a bunch of HTTP/TCP connections for a single client "page" view. This is done for performance reasons. So limiting the number of concurrent connections could definitely slow down the experience for clients (web browsers).
-- 
                                            digital man

Synchronet/BBS Terminology Definition #37:
FTSC = FidoNet Technical Standards Committee
Norco, CA WX: 95.4øF, 23.0% humidity, 6 mph NNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.