Hey, that thread helped me understanding the logic to prevent the refresh duplicates, but in the it still not bullet proof? Wouldn't it be really easy for someone to just add a random generated session id and tag it on the session_id parameter, and keep making form requests to your validation script. The validation script will always receive different generated sessions, thus making it really easy to flood your directory?

Perhaps, add a IP field and only allow 5 max request per? But then someone can trick the IP or perhaps connect to a list of proxies and take turns 1 by 1?

Theres really no reliable way is there?

In reply to Re^2: A good way to prevent \"spam flooding\"? by perleager
in thread A good way to prevent "spam flooding"? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.