Skip to content

Commit f997758

Browse files
committed
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.
Closes #12.
1 parent fbd57c8 commit f997758

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

index.html

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -204,9 +204,7 @@

Heuristics

204204
<section>
205205
<h4>Honeypotsh4>
206206
<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 <a href="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."
210208
p>
211209
section>
212210

0 commit comments

Comments
 (0)