You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revise the honeypot example so that it no longer makes a claim about a Web site that has changed (and which will continue to evolve) following publication of the Note. John Rochford observes that the text field in question no longer exists.
Copy file name to clipboardExpand all lines: index.html
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -204,9 +204,7 @@
Heuristics
204
204
<section>
205
205
<h4>Honeypotsh4>
206
206
<p>Providing a CAPTCHA visible to robots but not to humans appears to be sufficiently successful to be supported in several content management systems such as <ahref="https://www.drupal.org/project/honeypot">Drupal Honeypotsa> and in several commercial WordPress plugins. The form is created to attract robots and then hidden from the user by markup such as CSS-Hidden. It's an approach that is easily implemented even in hand authored markup and should be considered.
207
-
The Hilton Hotel Corporation has used a honeypot CAPTCHA on the Sign In page for <a
208
-
href="https://www.hiltonhonors.com">Hilton Honorsa>, its loyalty program website where a prominent focusable field is
209
-
labeled: "This field is for robots only. Please leave blank."
207
+
For example, a honeypot CAPTCHA formerly used on the Sign In page of a hotel Web site consisted of a prominent focusable field labeled: "This field is for robots only. Please leave blank."
0 commit comments