How to prevent malicious submissions, how to handle

How to prevent malicious submissions
How to prevent malicious submissions

------Solution--------------------
Validate with session. The verification code is too impersonal.

Or, after the submission succeeds, the header () to a new URL.
------Solution--------------------
Add verification code, only allow to submit from this site.
------Solution--------------------
After the submission is successful, the header ()
------Solution--------------------
Can csdn be maliciously submitted?
------Solution--------------------
Verify it, and also the session ..... You try the LS.
------Solution--------------------
Verification + session~
------Solution--------------------
There are usually several ways

1. Certified speakers, hehe.
2. Use refrence to determine whether a request from this site
3. Verification code.
1 Compare that what .... , hehe, 2 The main problem is which refrence can forge, 3. Lack of human nature,
Each has its advantages and disadvantages.

I do this plus a system certification, every day automatic change, the content of the same can not be submitted, continuous time interval is too short to submit, Ho Ho, see what good way to everyone.
------Solution--------------------
Cookie+timestamp
------Solution--------------------
Add verification code, only allow to submit from this site.

There is no use for this. Can forge a referer. And it's easy.
------Solution--------------------
It's usually a verification code.
------Solution--------------------
Continuous time interval is too short to commit, this empty cookie can be submitted again, it is best to write to the database, first log in, record the last commit time, so as to judge, to let malicious submitter also trouble

