Understood. Really appreciate for your nice time.
Thanks,
At 2015-05-20 21:00:33, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>
>
>On 5/20/15 4:22 AM, javalishixml wrote:
>> More detail information as below:
>>
&g
e again and again.
Is it a DDOS attack? Is there a good way to resolve it at httpd level?
At 2015-05-19 21:16:29, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>To whom it may concern,
>
>On 5/19/15 8:09 AM, javalishixm
5-05-19 20:01:00, "David kerber" wrote:
>On 5/19/2015 7:53 AM, javalishixml wrote:
>>
>>
>>
>>> I doubt you're going to be able to do this in httpd, unless you have a very
>>> simple, straight forward way of identifying the robots.
>> Ye
At 2015-05-19 19:35:26, "David kerber" wrote:
>On 5/19/2015 1:03 AM, javalishixml wrote:
>> Thanks a lot for your information.
>>
>>
>> This solution is based on tomcat level. If I always handle this issue at
>> java level, I'm afraid it has per
EGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>To whom it may concern,
>
>On 5/18/15 11:44 AM, javalishixml wrote:
>> I have a website. It is built by apache + tomcat.
>>
>> Now we make a lottery activity at this website. But we find that
>> some robots always
We find some client are always automatically fresh our lottery activity
At 2015-05-18 23:56:51, "David kerber" wrote:
>How would you tell that a request is from a robot?
>
>
>On 5/18/2015 11:44 AM, javalishixml wrote:
>> Hi,
>>
>> I have a
Hi,
I have a website. It is built by apache + tomcat.
Now we make a lottery activity at this website. But we find that some robots
always raise the duplicated requests to hit this lottery activity. It causes
that robots almost get all the awards.
So we just want to block these kind of duplicat
