Skip to content

Typings for Amazon WAF CAPTCHA request/response incorrect #5

@alexanderroidl

Description

@alexanderroidl

As seen in the 2Captcha documentation for Amazon WAF CAPTCHAs, challengeScript and captchaScript are missing in the type definition paramsAmazonWAF entirely:

export interface paramsAmazonWAF {
pageurl: string,
sitekey: string,
iv: string
context: string,
header_acao?: boolean,
pingback?: string,
soft_id?: number,
proxy?: string,
proxytype?: string,
}

Also the response typing is incorrect. For Amazon WAF it's actually structured like this:

interface CaptchaAnswerAmazonWAF {
  data: {
    captcha_voucher: string,
    existing_token: string
  },
  id: string
};

But it's implemented like this (data is NOT a string!!!):

interface CaptchaAnswer {
/** The solution to the captcha */
data: string,
/** The ID of the captcha solve */
id: string
}

I suspect many more typings will be incorrect as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions