Several times (3 times) after the submission of the Verification code ideas???

1 first three commits no graphical verification code appears
2 3 times after the graphics verification Code verification can be submitted

According to what is the number of submissions to be counted? Ip? A Cookie? Session, or other ideas?
If it is the SMS verification Code channel, others use the dynamic IP library to attack the words how to control?

Http://m.rong360.com/detail/2679?loan_limit=&loan_term=&repayment_type=0&guarantee_type=0&px=0 &org_type=0

Like the way this page is submitted

Reply content:

1 first three commits no graphical verification code appears
2 3 times after the graphics verification Code verification can be submitted

According to what is the number of submissions to be counted? Ip? A Cookie? Session, or other ideas?
If it is the SMS verification Code channel, others use the dynamic IP library to attack the words how to control?

Http://m.rong360.com/detail/2679?loan_limit=&loan_term=&repayment_type=0&guarantee_type=0&px=0 &org_type=0

Like the way this page is submitted

Can be memcache processed with or redis as a middleware cache, take the form of IP plus cookies to control malicious requests,

Let's do a cache. Memcache and Redis priority if you don't have both, then cookie.
Our company's thinking anti-theft chain IP repeatedly prohibit the front and rear two verification code and add a randomly generated token.

