> On Mar 24, 2017, at 11:19 AM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > 3. To "remediate" the problem, I've made some changes in the Web Structure > Settings > > a. set maximum concurrent web process to a much smaller number > than 32000 (128/256/512/1024) > (It looks like this might be the best thing to do) > Number of hits per hour/minute/second should be minimal in a > live situation > I'm think max hits/minute at peak time might be 100-200 > > b. Turned off automatic session management > Not sure if this will affect things positively or otherwise. > > 4. Any and all information regarding the above will be accepted with much > gratitude!
Use NGINX to proxy requests to 4D. It has all kinds of features to deal with this. And you can set it up so invalid requests never reach 4D in the first place. John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
