Answered my own question, damn, thought it was too simple.
You'd get around it by using the inputs label or other describing element.
You're getting out of the bounds of accessibility if those change too much.
Do you think the idea of dynamically named form inputs has any legs in the fight against automated form submissions?
Yeah, 'quite similar to a token so where's the advantage?' I hear you say.
but combined with dynamic ordering of the input elements (within limits), wouldn't this be enough (with some logic within your controller) to determine if the post contains the expected data and thereby fooling most automated methods? Except in the case of very short forms perhaps?
Drawback - Your users form completion order changes, but is this a big deal? You only register once.
Disclaimer:
First post from a web dev and something that annoys the hell out of me. Be gentle lol.
Slashdot Mirror
Answered my own question, damn, thought it was too simple. You'd get around it by using the inputs label or other describing element. You're getting out of the bounds of accessibility if those change too much.
Do you think the idea of dynamically named form inputs has any legs in the fight against automated form submissions? Yeah, 'quite similar to a token so where's the advantage?' I hear you say. but combined with dynamic ordering of the input elements (within limits), wouldn't this be enough (with some logic within your controller) to determine if the post contains the expected data and thereby fooling most automated methods? Except in the case of very short forms perhaps? Drawback - Your users form completion order changes, but is this a big deal? You only register once. Disclaimer: First post from a web dev and something that annoys the hell out of me. Be gentle lol.