Totally appropriate, IMHO. The problem is the test. When the problem is the 
problem, look at that. I’m guessing for 98% of websites powered by 4D, a DDOS 
is highly unlikely.


> On Mar 24, 2017, at 3:17 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> Hi Steve,
> Isn't that just patching for the test instead of the problem the test is
> trying to identify? Or am I missing something - which is entirely possible?
> 
> On Fri, Mar 24, 2017 at 9:31 AM, Stephen J. Orth via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> 
>> To get around this, we did a rather simple "trick"....
>> 
>> Since we know the format of every web request coming into our system, I
>> simply created a new method called "Utility_Web_Intrusion_Shutdown" which
>> looks like this:
>> 
>>     $minutes:=5*3600
>>     WEB STOP SERVER
>>     DELAY PROCESS(Current process;$minutes)
>>     WEB START SERVER
>> 
> 
> -- 
> Kirk Brooks
> San Francisco, CA
> =======================

**********************************************************************
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
**********************************************************************

Reply via email to