General BotDetect Options

BotDetect Simple Captcha API allows for introduction of captcha styles that are configurable by a non-programmer, and without access to your application source code. Those captcha styles consist of various combinations of image and sound algorithms and other settings.

By default, all BotDetect captcha options will be configured in botdetect.xml configuration file. If you want to change the configuration file path, please check this option.

CAPTCHA Configuration File Location

Description

Application configuration setting controlling the file system location of BotDetect Simple API configuration file.

ASP.NET: Default botdetect.xml location

The default location is of the botdetect.xml is in your ASP.NET application root folder.

Valid User Setting Values

Valid user Captcha configuration file location setting values are absolute file system paths, network paths (starting with "\\"), or relative paths.

Example Code

Application web.config configuration file setting:

<configuration>
  <appSettings>
    <add key="BDC_ConfigFileLocation" value="/resources/botdetect.xml"/>
  </appSettings>

  […]

</configuration>
or 
<configuration>
  <appSettings>
    <add key="BDC_ConfigFileLocation" value="C:\SharedResources\botdetect.xml"/>
  </appSettings>

  […]

</configuration>
or 
<configuration>
  <appSettings>
    <add key="BDC_ConfigFileLocation" value="\\NetworkShare\botdetect.xml"/>
  </appSettings>

  […]

</configuration>

ASP.NET Core appsettings.json configuration file setting:

{
  "BotDetect": {
    "ConfigFileLocation": "/resources/botdetect.xml"
  }
}

Java: Default botdetect.xml location

The default location is the /WEB-INF/botdetect.xml.

Valid User Setting Values

Valid user Captcha configuration file location setting values are absolute file system paths, network paths (starting with "\\"), or relative paths to the resources folder (starting with "/resources").

Example Code

Application web.xml configuration file setting:

<context-param>
  <param-name>BDC_configFileLocation</param-name>
  <param-value>/resources/botdetect.xml</param-value>
</context-param>
or 
<context-param>
  <param-name>BDC_configFileLocation</param-name>
  <param-value>C:\SharedResources\botdetect.xml</param-value>
</context-param>
or 
<context-param>
  <param-name>BDC_configFileLocation</param-name>
  <param-value>\\NetworkShare\botdetect.xml</param-value>
</context-param>

Spring Boot application.properties configuration file setting:

server.context_parameters.BDC_configFileLocation=/resources/botdetect.xml

Spring Boot ServletContextInitializer bean:

@Bean
public ServletContextInitializer initializer() {
  return new ServletContextInitializer() {

    @Override
    public void onStartup(ServletContext servletContext) throws ServletException {
      servletContext.setInitParameter("BDC_configFileLocation", "/resources/botdetect.xml");
    }
  };
}

Spring Boot InitParameterConfiguringServletContextInitializer bean:

@Bean
public InitParameterConfiguringServletContextInitializer initParamsInitializer() {
   Map<String, String> contextParams = new HashMap<>();
   contextParams.put("BDC_configFileLocation", "/resources/botdetect.xml");
   return new InitParameterConfiguringServletContextInitializer(contextParams);
}

PHP: Default botdetect.xml location

The default location in is the config/botdetect.xml

.

To change the configuration file path, edit the $BDC_Config_File_Path value in the simple-botdetect.php file.

Remarks

You should also always ensure that the web server worker process running your application has permissions to read from the custom configuration file path.

[back to the top of the page]

CAPTCHA Code Length

Description

Number of characters in randomly generated Captcha codes (answers to Captcha challenges).

Default

The default value is random (4-6 characters).

Valid User Setting Values

Valid user Captcha code length setting values are integers larger than 0 and smaller than 16.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <codeLength>4</codeLength>
    </captchaStyle>
  </captchaStyles>

</botdetect>
or 
<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <codeLength>4-6</codeLength>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

It is recommended to always randomize Captcha code length since it significantly increases Captcha security vs. automated analysis. To ensure randomization really affects each Captcha challenge generated, it should be performed through the application configuration file or user code executing for each Captcha challenge generation Http request. Randomization performed through Captcha object instance properties in form processing source code will only execute (and re-calculate the value used) on form GET or POST requests, instead on every Captcha challenge (image or sound) generation Http request.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Code Style

Description

Character types used to generate random Captcha codes.

Default

The default value is Alphanumeric.

Valid User Setting Values

Valid user Captcha code style setting values are members of the BotDetect CodeStyle enumeration (Alpha, Numeric, or Alphanumeric).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <codeStyle>Alpha</codeStyle>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Since entropy of the Captcha challenge depends on character set size to the power of Captcha code length, alpha codes should be slightly longer than alphanumeric ones (while numeric Captcha codes should be significantly longer) to achieve an appropriate level of Captcha security.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Disallowed Code Substrings

Description

Strings that should never occur in randomly generated Captcha codes. Can be both single characters (allows Captcha character set customization) and sequences of two or more characters (useful for swear words filtering, avoiding particular hard-to-read sequences etc.).

Default

The default value is empty (Captcha code filtering is optional).

Valid User Setting Values

Valid user disallowed Captcha code substring setting values are lists of arbitrary strings, in list object or CSV format. Whitespace is ignored, and disallowed substrings are not case-sensitive (because Captcha codes are case-insensitive as well).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <disallowedCodeSubstrings>d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,aa,bb,cc,abc,bca,cab</disallowedCodeSubstrings>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

The character set used for Captcha code generation is automatically chosen based on Captcha locale. Since each character needs to have its pronunciation recorded and available to BotDetect code, expanding that default character set to include new characters is not supported (it would break Captcha sound functionality). However, if a particular character is found hard to read, it can easily be excluded from randomly generated Captcha codes.

Furthermore, offensive or otherwise undesirable words and character sequences can be banned. Since Captcha codes are generally short, it doesn't make sense to use an actual dictionary of words, but simple short sequences that cover multiple disallowed values. E.g. to prevent the random generator from using both 'man', 'manners' and 'mannequin' in Captcha codes, it's enough to ban the 'man' sequence.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Code Timeout

Description

The time period after random Captcha code generation during which Captcha challenges based on it can be solved: when it expires, even correct inputs will be considered as invalid submissions.

Default

The default value is 1200 seconds (20 minutes).

Valid User Setting Values

Valid user Captcha code timeout setting values are integers larger than 30 and smaller than 7200 (i.e. between half a minute and 2 hours).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <codeTimeout>600</codeTimeout>

</botdetect>

Remarks

Reducing the Captcha code timeout is an optional security improvement that narrows the window of opportunity for attacks based on reusing the Captcha challenge on another site controlled by the attacker, proxying it to human solvers, or similar attempts to bypass the Captcha protection. However, to meet usability criteria, users filling out the form should always be given reasonably enough time to solve the Captcha challenge.

Since Captcha codes are stored in Session state by default, please note that if the configured code timeout is longer than the active Session timeout, Captcha validation will still fail if the user Session expires due to inactivity.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Test Mode Enabled

Description

Application configuration switch to use if you want to run automated tests that need to be able to submit a Captcha-protected form in QA environments.

Default

The default value is false.

Valid User Setting Values

Valid user Captcha test mode setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <testModeEnabled>true</testModeEnabled>

</botdetect>

Remarks

This setting is only supported in paid versions of BotDetect.

When test mode is enabled, it makes the Captcha challenge trivially solvable (always using "TEST" as the solution instead of a random sequence of characters). Be careful NEVER to enable this on production websites by mistake, since it will allow bots to trivially bypass the Captcha, but will still provide an obstacle for human users.

Because of the serious security implications if the Captcha test mode setting is misapplied, it can only be enabled globally for the whole application (individual forms and Captcha object instances can't change it), and will display a warning in generated Captcha container markup.

[back to the top of the page]

CAPTCHA Image Style

Description

The BotDetect drawing algorithm used to render Captcha codes in image Captcha challenges.

Default

The default value is random (an image style is chosen from all available values for each Captcha image generated).

Valid User Setting Values

Valid user Captcha image style setting values are members of the BotDetect ImageStyle enumeration. Please note that some image styles are restricted to paid versions of BotDetect, and will be ignored in free version implementations.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <imageStyle>Chipped,Fingerprints,Graffiti,Bullets</imageStyle>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

It's best to randomize the Captcha image style, since randomly choosing a style for each Captcha image generated provides the highest level of Captcha security against automated OCR analysis. To ensure randomization really affects each Captcha challenge generated, it should be performed through the application configuration file or user code executing for each Captcha challenge generation Http request. Randomization performed through Captcha object instance properties in form processing source code will only execute (and re-calculate the value used) on form GET or POST requests, instead on every Captcha challenge (image or sound) generation Http request.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Image Size

Description

Size of Captcha image challenges generated.

Default

The default value is 250 x 50 pixels.

Valid User Setting Values

Valid user Captcha image size setting values are integers: widths can be between 20 and 500 pixels and heights between 20 and 200 pixels.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <imageWidth>120</imageWidth>
      <imageHeight>35</imageHeight>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

To keep Captcha images reasonably readable, their width:height ratio should be approximately the same as the average Captcha code length.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Image Format

Description

Image format in which Captcha images will be generated and sent to the client.

Default

The default value is Jpeg.

Valid User Setting Values

Valid user Captcha image format setting values are members of the BotDetect ImageFormat enumeration (Jpeg, Png, Gif).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <imageFormat>Png</imageFormat>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Please note that some Captcha image styles will result in low-quality (pixelated) images when the image format is set to GIF, due to randomized color schemes and use of color gradients. When switching image formats, please take care to check the impact on Captcha image readability.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Color Mode

Description

Image color mode in which Captcha image color will be rendered and change it to other color on hover.

Default

The default value is None in free versions and GrayScale in paid versions of BotDetect.

Valid User Setting Values

Valid user Captcha image color mode setting values are members of the BotDetect ImageColorMode enumeration (Color, GrayScale, None).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <imageColorMode>GrayScale</imageColorMode>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid versions of BotDetect.

Image Color Mode Color

Captcha image is rendered in color, and it becomes greyscale on hover.

Image Color Mode GrayScale

Captcha image is rendered in grayscale, and it becomes color on hover.

Image Color Mode None

Captcha image is still rendered in color by default and nothing happens on hover.

[back to the top of the page]

CAPTCHA Custom Colors

Description

BotDetect allows Captcha image color scheme customization though two color points: a custom dark color and a custom light color.

Default

The default values are empty (Captcha color customization is optional).

Valid User Setting Values

Valid user Captcha custom dark / light color setting values are Html colors, so you can use both predefined color names and custom color hex values.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <customDarkColor>#ff00ff</customDarkColor>
      <customLightColor>#ffa500</customLightColor>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Since many Captcha drawing styles randomize the actual color used, the user-defined values are used as randomization starting points instead of absolute values. Furthermore, since some drawing styles use light text on a dark background, while other draw dark text on a light background, text and background colors are not set directly, but are referred to as simply the "dark" and the "light" color. This allows you to randomize the image drawing style, for example, and still keep a consistent color scheme adjusted to your website design.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Disabled Image Styles

Description

Application configuration setting that allows centralized temporary disabling of individual BotDetect image styles if there is ever an urgent issue that requires it.

Default

The default value is empty (image style disabling is an optional feature meant for short-term use during exceptional situations).

Valid User Setting Values

Valid user disabled image styles setting values are CSV strings of ImageStyle names (case-insensitive, separator whitespace is ignored).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <disabledImageStyles>Chipped,Lego,Wave</disabledImageStyles>

</botdetect>

Remarks

BotDetect image styles used on user forms can be configured in different ways (a single static value, a randomized value, a dynamic value that adapts to visitor behavior) and can apply to all Captcha instances in an application or be specific to a particular Captcha challenge placed on a single form.

If an urgent issue is ever discovered in a BotDetect image style implementation (e.g. a bug causing it to throw errors in certain circumstances, or a weakness allowing some forms of automated analysis to bypass it, or a memory leak etc.), users should be able to deactivate the problematic ImageStyle while they're waiting for issue resolution.

This BotDetect setting acts as a centralized application configuration switch which allows such image style deactivation, without requiring users to examine and possibly modify all of their source code that might be affected. It also makes it much easier to revert the change later when the issue gets fixed.

[back to the top of the page]

CAPTCHA Sound Enabled

Description

Is Captcha sound enabled.

Default

The default value is true.

Valid User Setting Values

Valid user Captcha sound enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundEnabled>false</soundEnabled>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Captcha sound can be disabled entirely (for example if you are using the free version of BotDetect, which only supports demo sound that is not actually accessible to human visitors) by setting this property to false.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Sound Style

Description

The BotDetect audio generation algorithm used to pronounce Captcha codes in sound Captcha challenges.

Default

The default value is random (a sound style is chosen from all available values for each Captcha sound generated).

Valid User Setting Values

Valid user Captcha sound style setting values are members of the BotDetect SoundStyle enumeration. Please note that some sound styles are restricted to paid versions of BotDetect, and will be ignored in free version implementations.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundStyle>Dispatch,RedAlert,Synth</soundStyle>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

It's best to randomize the Captcha sound style, since randomly choosing a style for each Captcha sound generated provides the highest level of Captcha security against automated audio analysis and voice recognition. To ensure randomization really affects each Captcha challenge generated, it should be performed through the application configuration file or user code executing for each Captcha challenge generation Http request. Randomization performed through Captcha object instance properties in form processing source code will only execute (and re-calculate the value used) on form GET or POST requests, instead on every Captcha challenge (image or sound) generation Http request.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Sound Format

Description

Audio format in which Captcha sounds will be generated and sent to the client.

Default

The default value is WavPcm16bit8kHzMono.

Valid User Setting Values

Valid user Captcha sound format setting values are members of the BotDetect SoundFormat enumeration (WavPcm16bit8kHzMono, WavPcm8bit8kHzMono).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundFormat>WavPcm8bit8kHzMono</soundFormat>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Using 8 bit sound instead of default 16 bits per example lowers the WAV file download size, but reduces sound quality.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Sound Regeneration Mode

Description

How will multiple consecutive requests for audio Captcha with the same Captcha code ("sound regeneration") be handled by BotDetect - a tradeoff of security, usability, and storage requirements.

Default

The default value is Limited.

Valid User Setting Values

Valid user Captcha sound regeneration mode setting values are members of the BotDetect SoundRegenerationMode enumeration (None, Limited, Unlimited).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundRegenerationMode>None</soundRegenerationMode>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

BotDetect defaults to limited sound regeneration as the most reasonable overall trade-off. At user discretion, higher security and usability can be achieved by disabling sound regeneration at the cost of significant amounts of server-side storage space. Unlimited sound regeneration is not recommended due to low security, but is left as an option for backwards-compatibility.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

Sound Regeneration Mode Option Details

Sound Regeneration Mode None Limited Unlimited
Security ★★★★★ ★★★★☆ ★☆☆☆☆
Usability ★★★★★ ★★★★☆ ★★★★★
Storage Requirements ★★★★★ ★☆☆☆☆ ★☆☆☆☆
Sound Regeneration Mode None

Generate only one sound response per Captcha code, cache it on the server, and serve it for all consecutive sound requests.

  • High security: Comparative analysis of multiple sounds is impossible since only one sound response exists per Captcha code.
  • High usability: Works consistently across all browsers, regardless of their Html5 audio support and without depending on JavaScript functionality.
  • High storage requirements: The generated sound bytes must be stored in Session state, consuming server memory or other storage medium for each Captcha code requested as Captcha audio.
Sound Regeneration Mode Limited

Allow generation of a limited number of different sound responses (the minimum required to make Captcha audio work in all supported client browsers and devices), and automatically change the Captcha code on the client for consecutive sound requests if needed and possible.

  • Good security: Comparative analysis of multiple sounds is severely hampered, since the small number of sound responses available does not provide enough information to seriously undermine Captcha security.
  • Good usability: Since Captcha sound will only be served a small number of times for the same Captcha code (returning an error after the limit has been hit), observed behavior depends on client browser capabilities:
    • Modern Html5 Wav audio compatible browsers will always replay the same sound on consecutive sound icon clicks, without requesting a regenerated sound from the server.
    • Older browsers without support for client-side audio replay must detect consecutive sound icon clicks that might trigger the sound regeneration limit on the server and automatically change the Captcha code (by reloading the Captcha image) to ensure sound will play properly. For each sound icon click after the first one, the Captcha image will be changed before audio is played.
    • Browsers without JavaScript capability (and bots) will have to reload the form to get a new Captcha code to make the sound work again after the regeneration limit had been hit.
  • Low storage requirements: Generated sound responses don't need to be stored on the server.
Sound Regeneration Mode Unlimited

Each audio request will generate a new Captcha sound response (previous BotDetect version behavior).

  • Low security: Comparative analysis of multiple sounds for the same Captcha code allows for higher accuracy of automated recognition.
  • High usability: Works consistently across all browsers, regardless of their Html5 audio support and without depending on JavaScript functionality.
  • Low storage requirements: Generated sound responses don't need to be stored on the server.

[back to the top of the page]

CAPTCHA Sound Packages Folder

Description

Application configuration setting controlling the file system location of BotDetect sound resources required for Captcha audio.

Default

The default value is the Bin\BotDetectSounds subfolder in your ASP.NET application folder.

Valid User Setting Values

Valid user Captcha sound packages folder setting values are absolute file system paths, network paths (starting with "\\"), or relative paths to the "~\" folder.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <soundPackagesFolder>~\BotDetectSounds</soundPackagesFolder>

</botdetect>
or 
<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <soundPackagesFolder>C:\SharedResources\BotDetectSounds</soundPackagesFolder>

</botdetect>
or 
<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <soundPackagesFolder>\\NetworkShare\BotDetectSounds</soundPackagesFolder>

</botdetect>

Remarks

You should also always ensure that the web server worker process running your ASP.NET application has permissions to read from the custom folder path.

[back to the top of the page]

Warn About Missing CAPTCHA Sound Packages

Description

Application configuration setting that controls whether BotDetect disables (greys-out and prevents clicks on) the Captcha sound icon and displays a warning tooltip when the sound package file containing character pronunciations for the currently set Captcha locale can not be found.

Default

The default value is true (display a warning when the required .bdsp file cannot be found).

Valid User Setting Values

Valid user warn about missing sound packages setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <warnAboutMissingSoundPackages>false</warnAboutMissingSoundPackages>

</botdetect>

Remarks

Warnings about missing sound packages help during development and deployment, so you don't mistakenly forget to download and copy the needed files. However, this warning is not meant for (and should never be seen by) site visitors. So if you didn't copy a particular sound package because you intentionally don't want to support audio Captcha sounds in that language, you can disable the warning (and the sound icon for such locales).

[back to the top of the page]

CAPTCHA Disabled Sound Styles

Description

Application configuration setting that allows centralized temporary disabling of individual BotDetect sound styles if there is ever an urgent issue that requires it.

Default

The default value is empty (sound style disabling is an optional feature meant for short-term use during exceptional situations).

Valid User Setting Values

Valid user disabled sound styles setting values are CSV strings of SoundStyle names (case-insensitive, separator whitespace is ignored).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <disabledSoundStyles>RedAlert,HiveMind</disabledSoundStyles>

</botdetect>

Remarks

BotDetect sound styles used on user forms can be configured in different ways (a single static value, a randomized value, a dynamic value that adapts to visitor behavior) and can apply to all Captcha instances in an application or be specific to a particular Captcha challenge placed on a single form.

If an urgent issue is ever discovered in a BotDetect sound style implementation (e.g. a bug causing it to throw errors in certain circumstances, or a weakness allowing some forms of automated analysis to bypass it, or a memory leak etc.), users should be able to deactivate the problematic SoundStyle while they're waiting for issue resolution.

This BotDetect setting acts as a centralized application configuration switch which allows such sound style deactivation, without requiring users to examine and possibly modify all of their source code that might be affected. It also makes it much easier to revert the change later when the issue gets fixed.

[back to the top of the page]

CAPTCHA Locale

Description

Captcha locale string, determining the exact character set used for random Captcha code generation and the pronunciation language used for sound Captcha generation.

Default

The default value is en-US.

Valid User Setting Values

Valid user Captcha locale setting values are composed of ISO language codes (for example en, ru, cmn, ...), charset codes (for example ja-Hira uses Japanese Hiragana characters, while ja-Kana uses Japanese Katakana characters) and country codes (for example en-US and en-GB differ in the pronunciation used).

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <locale>en-GB</locale>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Check the BotDetect localization page to find the list of currently supported locales, and download the pronunciation resources required for Captcha sounds.

If you use a right-to-left locale setting like Arabic or Hebrew, you should also set the appropriate text direction on the textbox element used for Captcha code retyping (dir="rtl").

Depending on your OS version and the locale you want to use, you also might have to install the appropriate Windows localization package, containing fonts supporting the required non-latin characters.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA Image Tooltip

Description

The alternative text of the Captcha image Html element.

Default

The default value is "Retype the CAPTCHA code from the image".

Valid User Setting Values

Valid user Captcha image tooltip setting values are arbitrary strings.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <imageTooltip>Custom Captcha image tooltip</imageTooltip>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Sound Tooltip

Description

Tooltip of the Captcha sound icon.

Default

The default value is "Speak the CAPTCHA code".

Valid User Setting Values

Valid user Captcha sound tooltip setting values are arbitrary strings.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundTooltip>Custom Captcha sound icon tooltip</soundTooltip>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Reload Tooltip

Description

Tooltip of the Captcha reload icon.

Default

The default value is "Change the CAPTCHA code".

Valid User Setting Values

Valid user Captcha reload tooltip setting values are arbitrary strings.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <reloadTooltip>Custom Captcha reload icon tooltip</reloadTooltip>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Help Link Text

Description

Text or tooltip of the Captcha help link, depending on help link mode.

Default

The default value depends on the width of the Captcha image.

Valid User Setting Values

Valid user Captcha help link setting values are strings at least 4 characters long.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <helpLinkText>Custom Captcha help link text</helpLinkText>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Description

Url of the localized Captcha help page the help link points to.

Default

The default value depends on Captcha locale.

Valid User Setting Values

Valid user Captcha help link url setting values are absolute or relative Urls.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <helpLinkUrl>custom-captcha-help-page.html</helpLinkUrl>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid versions of BotDetect.

[back to the top of the page]

CAPTCHA Reload Enabled

Description

Is Captcha reloading (changing the Captcha code because the current one is too hard to read) enabled.

Default

The default value is true.

Valid User Setting Values

Valid user Captcha reload enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <reloadEnabled>false</reloadEnabled>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Requesting a new Captcha challenge on the current form requires client-side scripting, so the reload icon is only shown in browsers that have JavaScript enabled. When JavaScript is disabled or unsupported, the visitor can still get a different Captcha challenge by reloading the form.

[back to the top of the page]

Use Small CAPTCHA Icons

Description

Default BotDetect Captcha icons are 22x22 pixels large, but there is also a smaller set of 17x17 px icons used when the default ones are too large. This settings allows you to control which icon set will be used.

Default

The default value is true when the Captcha image height is < 50px, and false otherwise.

Valid User Setting Values

Valid user use small Captcha icons setting values are booleans: setting this value to true will force BotDetect to use small built-in icons, while false will disable automatic switching to small icons depending on image height.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <useSmallIcons>false</useSmallIcons>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting only applies to default BotDetect icons, and should not be used in combination with user-defined icons.

[back to the top of the page]

Use Horizontal CAPTCHA Icons

Description

BotDetect displays the Captcha sound and reload icon one below the other by default, and switches to displaying them one beside the other when Captcha images are small enough. This setting allows you to control which BotDetect icon layout will be used.

Default

The default value is true when the Captcha image height is < 40px, and false otherwise.

Valid User Setting Values

Valid user use horizontal Captcha icons setting values are booleans: setting this value to true will force BotDetect to use a horizontal icon layout, while false will disable automatic switching to horizontal icons depending on image height.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <useHorizontalIcons>false</useHorizontalIcons>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting only applies to default BotDetect icons, and should not be used in combination with user-defined icons.

[back to the top of the page]

CAPTCHA Sound Icon URL

Description

Url of the optional custom Captcha sound icon that will be used instead of the default one.

Default

The default value is "BotDetect.ashx?get=sound-icon".

Valid User Setting Values

Valid user Captcha sound icon setting values are absolute or relative Urls. When specifying a custom Captcha sound icon, you should make sure its filename includes "icon", and also provide a disabled variation of the icon that will be shown during sound playback (to prevent the user from clicking the icon multiple times). The disabled sound icon variant should be the same size and have a filename based on the active one ("icon" replaced with "disabled-icon").

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundIconUrl>/custom-sound-icon.gif</soundIconUrl>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Reload Icon URL

Description

Url of the optional custom Captcha reload icon that will be used instead of the default one.

Default

The default value is "BotDetect.ashx?get=reload-icon".

Valid User Setting Values

Valid user Captcha reload icon setting values are absolute or relative Urls. When specifying a custom Captcha reload icon, you should make sure its filename includes "icon", and also provide a disabled variation of the icon that will be shown while the browser is waiting to fetch a new Captcha challenge from the server (to prevent the user from clicking the icon multiple times). The disabled reload icon variant should be the same size and have a filename based on the active one ("icon" replaced with "disabled-icon").

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <reloadIconUrl>/custom-reload-icon.gif</reloadIconUrl>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Icons Div Width

Description

Custom width of the Captcha icons <div> element.

Default

The default value depends on Captcha image height, since BotDetect will automatically determine default icon size and position to match it.

Valid User Setting Values

Valid user Captcha icons div width setting values are positive integers.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <iconsDivWidth>25</iconsDivWidth>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

If your custom Captcha icons are not of the same size as the default BotDetect ones (22x22 px), the useHorizontalIcons setting won't be able to control the icon layout correctly. You can control whether your custom icons will be displayed one beneath the other or one beside the other by setting an appropriate icons div width: setting it to at least twice the icon width + 8px of padding will result in horizontal icon layout, while smaller values will result in vertical icon layout.

[back to the top of the page]

Description

Will Captcha markup include a link to a Captcha help page providing Captcha instructions and explanations for form users.

Default

The default value is true.

Valid User Setting Values

Valid user help link enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <helpLinkEnabled>false</helpLinkEnabled>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]


Description

How will the Captcha help link be displayed.

Default

The default value is TEXT.

Valid User Setting Values

Valid user Captcha help link mode setting values are members of the BotDetect HelpLinkMode enumeration ("IMAGE" or "TEXT").

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <helpLinkMode>IMAGE</helpLinkMode>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

When using the IMAGE help link mode, Captcha image is wrapped in a link, and clicking it opens the help page in a new browser tab. This mode takes less space, but can lead to accidental clicks (particularly by mobile visitors).

When using the TEXT help link mode, Captcha image height is automatically reduced by 10 px and a text link to the Captcha help page is inserted below it. If this makes the Captcha images less readable, you can compensate by increasing the Captcha image height.

Since this setting affects Captcha challenge (image or sound) generation in Http requests separate from form execution, it needs to be saved in Session state when set through Captcha object instance properties in form source, consuming server resources and reverting to default when the Session expires. It is recommended to set it through the application configuration file, or user code executing for each Captcha challenge generation Http request instead.

[back to the top of the page]

CAPTCHA TabIndex

Description

Starting tabindex for the Captcha container Html markup elements.

Default

The default value is empty (Captcha elements won't have an explicit tabindex set).

Valid User Setting Values

Valid user Captcha tabindex setting values are integers, and -1 is a special value that will disable tabbing over Captcha elements in most browsers.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <tabIndex>10</tabIndex>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

There are three keyboard-selectable Captcha markup elements: the Captcha help link, the Captcha sound icon and the Captcha reload icon. Depending on your settings (whether the Captcha help link is enabled, are Captcha sounds enabled, is Captcha reloading enabled), the next available tabindex on the page can be from 0 to 3 greater than this value.

Since tabindex values depend on the particular form where the Captcha challenge is placed, this BotDetect setting can not be set through application config files, but only in form source.

[back to the top of the page]

Add CAPTCHA CSS Include

Description

Should the BotDetect layout stylesheet be included by the generated Captcha container markup.

Default

The default value is true.

Valid User Setting Values

Valid user add Captcha CSS include setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <addCssInclude>false</addCssInclude>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting will usually only be set to false if you have multiple Captcha instances on the same form and only want the first one's markup to include the required BotDetect layout stylesheet.

[back to the top of the page]

CAPTCHA Additional CSS Classes

Description

User-defined CSS classes that will be added to the BotDetect Captcha container <div>.

Default

The default value is empty.

Valid User Setting Values

Valid user additional CSS classes setting values are strings containing desired class names in standard space-delimited CSS class format. CSS style declarations for these custom classes must be defined in a user stylesheet added to the page.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <additionalCssClasses>class1 class2 class3</additionalCssClasses>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

CAPTCHA Additional Inline CSS

Description

User-defined CSS style declarations that will be added as inline style of the BotDetect CAPTCHA container <div>.

Default

The default value is empty.

Valid User Setting Values

Valid user additional CSS style setting values are strings containing desired CSS style declarations in standard semicolon-delimited CSS style format.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <additionalInlineCss>border: 4px solid #fff; background-color: #f8f8f8;</additionalInlineCss>
    </captchaStyle>
  </captchaStyles>

</botdetect>

[back to the top of the page]

Add CAPTCHA Script Include

Description

Should the BotDetect JavaScript client-side script code be included by the generated Captcha container markup.

Default

The default value is true.

Valid User Setting Values

Valid user add script include setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <addScriptInclude>false</addScriptInclude>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting will usually only be set to false if you have multiple Captcha instances on the same form and only want the first one's markup to include the required BotDetect client-side code. Another possible use is when you manually add the necessary <script> include to page <head>, possibly combined with other JavaScript code and minified to reduce the number of Http requests made by the page.

[back to the top of the page]

CAPTCHA Auto Uppercase Input

Description

Should user Captcha code input be automatically uppercased on the fly.

Default

The default value is true.

Valid User Setting Values

Valid user auto uppercase input setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <autoUppercaseInput>false</autoUppercaseInput>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Since Captcha validation is not and should not be case-sensitive (it would hinder human visitors more than bots, and how would case differences be communicated through audio Captcha in all supported pronunciation languages?), automatically uppercasing user input is a small usability improvement that helps communicate the case-insensitivity of the Captcha challenge to users.

[back to the top of the page]

CAPTCHA Auto Focus Input

Description

Should the Captcha code input textbox automatically be assigned focus on all Captcha sound and Captcha reload icon clicks, allowing the users to more easily type in the code as they hear it or as the new image loads.

Default

The default value is true.

Valid User Setting Values

Valid user auto focus input setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <autoFocusInput>false</autoFocusInput>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Automatic input element focusing is not triggered by auto-reloading of expired Captcha challenges, since the user might be filling out another field on the form when the auto-reload starts and shouldn't be distracted.

[back to the top of the page]

CAPTCHA Auto Clear Input

Description

Should the Captcha user input textbox automatically be cleared on all reload icon clicks and auto-reloads of expired Captcha codes.

Default

The default value is true.

Valid User Setting Values

Valid user auto clear input setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <autoClearInput>false</autoClearInput>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Automatic input clearing is a small usability improvement: since any previous user input will be invalidated by Captcha reloading, it helps so users don't have to delete the previous input themselves.

[back to the top of the page]

Auto Reload Expired Captchas

Description

Should Captcha challenges automatically be reloaded when the Captcha code expires (controlled by the Captcha code timeout property).

Default

The default value is true.

Valid User Setting Values

Valid user auto reload expired Captchas setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <autoReloadExpiredCaptchas>false</autoReloadExpiredCaptchas>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

Automatic reloading of expired Captcha codes allows you to have a short Captcha code timeout (e.g. 2 minutes) to narrow the window of opportunity for Captcha reusing on other sites or human-solver-powered bots, and actual visitors can still fill out your form at their own pace and without rushing (since the Captcha image will be reloaded automatically when it is no longer valid).

[back to the top of the page]

CAPTCHA Auto Reload Timeout

Description

Time period in seconds after which automatic reloading of expired Captcha challenges will cease.

Default

The default value is 7200 seconds (2 hours).

Valid User Setting Values

Valid user auto reload timeout setting values are positive integers.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <autoReloadTimeout>3600</autoReloadTimeout>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This timeout prevents indefinite extension of the visitor Session, when the user leaves the form open in a background browser tab over the weekend for example.

[back to the top of the page]

CAPTCHA Sound Start Delay

Description

Starting delay (in milliseconds) of Captcha audio JavaScript playback.

Default

The default value is 0 (no delay).

Valid User Setting Values

Valid user Captcha sound start delay setting values are positive integers.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <soundStartDelay>1000</soundStartDelay>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

An initial delay before browser sound playback can be useful for improving usability of the Captcha audio for blind people using JAWS or similar screen readers. Such assistive technology will read the label associated with the Captcha code textbox and start sound playback simultaneously when the sound icon is activated (since Captcha sound playing automatically focuses the Captcha code textbox by default). Setting this delay to e.g. 2000 (2 seconds) will give the user time to hear both the pronounced label and the Captcha sound clearly.

[back to the top of the page]

CAPTCHA Remote Scripts Enabled

Description

Should BotDetect also add a remote JavaScript include (remote.captcha.com/include.js) loaded from the captcha.com server (which is currently used only for stats, but is planned to develop into additional Captcha functionality).

Default

The default value is true.

Valid User Setting Values

Valid user remote script enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <captchaStyles>
    <captchaStyle>
      <name>ExampleCaptcha</name>
      <remoteScriptEnabled>false</remoteScriptEnabled>
    </captchaStyle>
  </captchaStyles>

</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

[back to the top of the page]

CAPTCHA Redis Persistence Provider

Description

Switching BotDetect captcha persistence provider to using Redis, which is used to store Captcha data.

Default

The default persistence provider is "SQLite" (SQLite3 Database).

Example Code

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>
  
  <captchaPersistence>
    <persistenceType>Redis</persistenceType>
    <endpoints>redis0:6380,redis1:6380</endpoints>
    <abortOnConnectFail>true</abortOnConnectFail>
    <allowAdmin>false</allowAdmin>
    <channelPrefix>null</channelPrefix>
    <connectRetry>3</connectRetry>
    <connectTimeout>5000</connectTimeout>
    <configurationChannel></configurationChannel>
    <configCheckSeconds>60</configCheckSeconds>
    <defaultDatabase>null</defaultDatabase>
    <keepAlive>-1</keepAlive>
    <clientName>null</clientName>
    <password>null</password>
    <proxy>None</proxy>
    <resolveDns>false</resolveDns>
    <responseTimeout>1000</responseTimeout>
    <serviceName>null</serviceName>
    <ssl>false</ssl>
    <sslHost>null</sslHost>
    <sslProtocols>null</sslProtocols>
    <syncTimeout>1000</syncTimeout>
    <tieBreaker></tieBreaker>
    <defaultVersion></defaultVersion>
    <writeBuffer>4096</writeBuffer>
  </captchaPersistence>
  
</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

The BotDetect Redis configuration options are implemented based on StackExchange.Redis's configuration.

[back to the top of the page]

CAPTCHA Memcached Persistence Provider

Description

Switching BotDetect captcha persistence provider to using Memcached, which is used to store Captcha data.

Default

The default persistence provider is "SQLite" (SQLite3 Database).

Example Code

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>
  
  <captchaPersistence>
    <persistenceType>Memcached</persistenceType>
    <address>127.0.0.1:11211</address>
    <protocol>Binary</protocol>
    <minPoolSize>10</minPoolSize>
    <maxPoolSize>20</maxPoolSize>
    <connectionTimeout>00:00:10</connectionTimeout>
    <queueTimeout>00:00:00.100</queueTimeout>
    <deadTimeout>00:00:10</deadTimeout>
    <receiveTimeout></receiveTimeout>
    <keepAliveStartDelay></keepAliveStartDelay>
    <keepAliveInterval></keepAliveInterval>
  </captchaPersistence>
  
</botdetect>

Remarks

This setting is only supported in paid version of BotDetect.

The BotDetect Memcached configuration options are implemented based on EnyimMemcached's configuration.

[back to the top of the page]

Your App Backend Host Name

Description

The base url of your website where you have installed Captcha library as a captcha endpoint. It allows usage of an absolute captcha handler url when backend and frontend applications are hosted on different sub-domains of the same domain.

Default

The default value is empty.

Valid User Setting Values

Valid user setting values are url strings.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <yourAppBackendHostName>https://example.com</yourAppBackendHostName>

</botdetect>

[back to the top of the page]

Captcha Endpoint CORS Header

Description

Should BotDetect add Access-Control-Allow-Origin header in Captcha resource responses for CORS scenarios.

Default

The default value is false.

Valid User Setting Values

  • accessControlAllowOriginHeaderEnabled: true or false
  • accessControlAllowOriginHeaderValue: your frontend app host name

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>
  
  <captchaEndpoint>
    <accessControlAllowOriginHeaderEnabled>true</accessControlAllowOriginHeaderEnabled>
    <accessControlAllowOriginHeaderValue>https://your-frontend-app.com</accessControlAllowOriginHeaderValue>
  </captchaEndpoint>
  
</botdetect>

[back to the top of the page]

CAPTCHA Endpoint Path

Description

Path of the BotDetect ASP.NET used for processing Captcha image, sound and Ajax validation requests, as well as accessing all BotDetect public resources (Captcha icons, layout stylesheet, client-script include).

Valid User Setting Values

Valid user Captcha endpoint path setting values are path (filename + extension) strings.

Example Code

ASP.NET Core appsettings.json configuration file setting:

{
  "BotDetect": {
    "CaptchaEndpointPath": "simple-captcha-endpoint.ashx"
  }
}

[back to the top of the page]

CAPTCHA HttpHandler Troubleshooting Enabled

Description

Should Captcha HttpHandler diagnostics be run.

Default

The default value is false.

Valid User Setting Values

Valid user Captcha HttpHandler troubleshooting enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <httpHandlerTroubleshootingEnabled>true</httpHandlerTroubleshootingEnabled>

</botdetect>

Remarks

HttpHandler troubleshooting might be useful while developing your BotDetect-protected form, but should be turned off for production deployments after you ensure the Captcha challenges are working properly.

[back to the top of the page]

CAPTCHA Request Filter Enabled

Description

Should the custom Captcha Http request validator be run.

Default

The default value is true.

Valid User Setting Values

Valid user Captcha request filter enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <requestFilterEnabled>false</requestFilterEnabled>

</botdetect>

Remarks

The custom Captcha Http request validator counts the number of repeated Captcha HttpHandler requests with the exact same query string, and stops generating Captcha challenges if a certain repetition threshold is exceeded. Human users using regular browsers will mostly request each Captcha challenge with a unique query string (a small number of repeated requests is possible depending on the browser), while simple scraping bots will often repeat the same request a large number of times, wasting server resources.

Current qequest count is stored in ASP.NET HttpRuntime.Cache, with sliding expiration using the same timeout as the current ASP.NET Session timeout (which controls most aspects of Captcha functionality anyway). When the allowed repeated request count is exceeded, the Captcha HttpHandler will just send a 400 Bad Request response to the client instead of generating a new Captcha challenge for a bot.

This kind of Http request validation is a simple optional Captcha workflow optimization meant primarily to conserve server CPU resources, and can be turned off without compromising Captcha security if you want to conserve server memory (used for ASP.NET HttpRuntime.Cache storage) instead.

[back to the top of the page]

CAPTCHA Request Filter Repeated Requests Allowed

Description

How many repeated Captcha HttpHandler requests using the exact same query string will be allowed in a short time period.

Default

The default value is 5.

Valid User Setting Values

Valid user Captcha request filter repeated requests allowed setting values are positive integers between 1 and 100.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <requestFilterRepeatedRequestsAllowed>10</requestFilterRepeatedRequestsAllowed>

</botdetect>

Remarks

You will typically only increase this value if the Captcha request filter is for some reason causing issues with legitimate user behavior in your application.

[back to the top of the page]

CAPTCHA Logging Provider

Description

Fully-qualified name of a .NET class implementing the BotDetect.Logging.ILoggingProvider interface, loaded by the current ASP.NET application and used to process all BotDetect logging calls.

Default

The default value is "BotDetect.Logging.NullLoggingProvider, BotDetect".

Valid User Setting Values

Valid user Captcha logging provider setting values are fully qualified names of .NET classes available in the current ASP.NET application and implementing the BotDetect.Logging.ILoggingProvider interface.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <loggingProvider>BotDetect.Logging.NullLoggingProvider, BotDetect</loggingProvider>

</botdetect>

Remarks

The default BotDetect.Logging.NullLoggingProvider will ignore all Captcha log statements. If you want to use log4net to log Captcha errors and a detailed execution trace, switch to "BotDetect.Logging.Log4NetLoggingProvider, BotDetect.Troubleshooting" (BotDetect.Troubleshooting.dll and a redistribution of log4net.dll is included in the BotDetect ASP.NET Captcha installation). If you want to send the Captcha log to a different logging provider, you will have to find or implement a class that uses the desired back-end to implement the BotDetect.Logging.ILoggingProvider interface.

Please note that BotDetect uses reflection to instantiate custom logging classes, so such Captcha logging will only work in applications with the required execution permissions.

[back to the top of the page]

CAPTCHA Error Logging Enabled

Description

Should exceptions originating in BotDetect code be logged to the currently active Captcha logging provider.

Default

The default value is false.

Valid User Setting Values

Valid user Captcha error logging enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <errorLoggingEnabled>true</errorLoggingEnabled>

</botdetect>

[back to the top of the page]

CAPTCHA Trace Logging Enabled

Description

Should a detailed trace of the Captcha generation and validation workflow be logged to the currently active Captcha logging provider.

Default

The default value is false.

Valid User Setting Values

Valid user Captcha Trace logging enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <traceLoggingEnabled>true</traceLoggingEnabled>

</botdetect>

[back to the top of the page]

CAPTCHA Trace Logging Event Filter

Description

Filter which Captcha events will be included in the BotDetect trace log.

Default

The default value is ".*".

Valid User Setting Values

Valid user Captcha trace event filter setting values are strings with regular expressions that will be matched against BotDetect event names. Event names used by BotDetect code are: InitializedWebCaptcha, GeneratingCaptchaCode, GeneratedCaptchaCode, GeneratingCaptchaImage, GeneratedCaptchaImage, GeneratingCaptchaSound, GeneratedCaptchaSound, ValidatingUserInput, ValidatedUserInput, Warning. This makes it easy to construct a regex expression that will filter and log only the BotDetect events you are interested in.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <traceLoggingEventFilter>(Initialized)|(Generated)</traceLoggingEventFilter>

</botdetect>
or 
<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <traceLoggingEventFilter>CaptchaImage</traceLoggingEventFilter>

</botdetect>
or 
<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <traceLoggingEventFilter>Warning</traceLoggingEventFilter>

</botdetect>

[back to the top of the page]

FIPS Compliance Enabled

Description

Is FIPS Compliance enabled.

Default

The default value is false.

Valid User Setting Values

Valid user FIPS Compliance enabled setting values are booleans.

Example Code

Application botdetect.xml configuration file setting:

<?xml version="1.0" encoding="UTF-8"?>
<botdetect>

  <fipsComplianceEnabled>true</fipsComplianceEnabled>

</botdetect>

Remarks

Captcha FIPS Compliance can be enabled entirely by setting this property to true.

Please note FIPSComplianceEnabled setting is ignored in the free version of BotDetect.

[back to the top of the page]

Please Note

This document is not up to date. We are working on fixing it. Your Simple API integration efforts should start with one of the following four step-by-step integration guides: Angular Captcha, AngularJS Captcha, jQuery Captcha, React Captcha.

© Captcha, Inc. 2004-2023. All rights reserved.

BotDetect, BotDetect CAPTCHA, Lanap, Lanap CAPTCHA, Lanap BotDetect, Lanap BotDetect CAPTCHA, Lanapsoft, Lanapsoft CAPTCHA, Lanapsoft BotDetect, Lanapsoft BotDetect CAPTCHA, and Lanap Software are trademarks of Captcha, Inc. All other product, brand, and company names are mentioned for identification purposes only and are trademarks or registered trademarks of their respective owners.

Captcha, Inc. -- formerly: Lanapsoft, Inc. / Lanap, Inc.