[Bug]: log in to self-hosted Browsertrix fails due to the wrong content type

[annappropriate]

ArchiveWeb.page Version

0.14.1

What did you expect to happen? What happened instead?

I have a self-hosted Browsertrix instance set up, and I would like to connect the ArchiveWeb.page extension to it. I can successfully log in via the Browsertrix web interface.

Here is a curl command one can obtain from the web UI login process, which runs successfully:

$ curl 'https://MY_DOMAIN/api/auth/jwt/login' \
                          -H 'Accept: */*' \
                          -H 'Accept-Language: en-US,en;q=0.9,uk;q=0.8' \
                          -H 'Connection: keep-alive' \
                          -H 'Content-Type: application/x-www-form-urlencoded' \
                          -H 'Origin: https://MY_DOMAIN' \
                          -H 'Referer: https://MY_DOMAIN/log-in' \
                          -H 'Sec-Fetch-Dest: empty' \
                          -H 'Sec-Fetch-Mode: cors' \
                          -H 'Sec-Fetch-Site: same-origin' \
                          -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36' \
                          -H 'sec-ch-ua: "Chromium";v="130", "Google Chrome";v="130", "Not?A_Brand";v="99"' \
                          -H 'sec-ch-ua-mobile: ?0' \
                          -H 'sec-ch-ua-platform: "Linux"' \
                          --data-raw 'grant_type=password&username=USER%40EMAIL.com&password=PASSWORD' \
                          --insecure | jq .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   582  100   489  100    93    997    189 --:--:-- --:--:-- --:--:--  1187
{
  "access_token": "x",
  "token_type": "bearer",
  "user_info": {
    "id": "x",
    "name": "Anna",
    "email": "[email protected]",
    "is_superuser": true,
    "is_verified": false,
    "orgs": [
      {
        "id": "x",
        "name": "x",
        "slug": "x",
        "default": true,
        "role": 100
      }
    ]
  }
}

And here is what's sent from the extension:

$ curl 'https://MY_DOMAIN/api/auth/jwt/login' \
               -H 'sec-ch-ua-platform: "Linux"' \
               -H 'Referer;' \
               -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36' \
               -H 'Accept: */*' \
               -H 'sec-ch-ua: "Chromium";v="130", "Google Chrome";v="130", "Not?A_Brand";v="99"' \
               -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryEFdE41prJFPvcemD' \
               -H 'sec-ch-ua-mobile: ?0' \
               --data-raw \$'------WebKitFormBoundaryEFdE41prJFPvcemD\r\nContent-Disposition: form-data; name="username"\r\n\r\[email protected]\r\n------WebKitFormBoundaryEFdE41prJFPvcemD\r\nContent-Disposition: form-data; name="password"\r\n\r\nPASSWORD\r\n------WebKitFormBoundaryEFdE41prJFPvcemD--\r\n' | jq .
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   579  100   274  100   305   1786   1988 --:--:-- --:--:-- --:--:--  3784
{
  "detail": [
    {
      "type": "missing",
      "loc": [
        "body",
        "username"
      ],
      "msg": "Field required",
      "input": null,
      "url": "https://errors.pydantic.dev/2.8/v/missing"
    },
    {
      "type": "missing",
      "loc": [
        "body",
        "password"
      ],
      "msg": "Field required",
      "input": null,
      "url": "https://errors.pydantic.dev/2.8/v/missing"
    }
  ]
}

The issue seems to be in the different content types and payloads. According to the API spec, application/x-www-form-urlencoded is the correct content type: https://docs.browsertrix.com/api/#tag/auth/operation/login_api_auth_jwt_login_post

Could you please fix the login field to use the correct content type?

Step-by-step reproduction instructions

1. Go to the extension settings
2. Navigate to settings -> Browsertix tab
3. Fill in custom server URL, login and password
4. Click "Save"

Additional details

No response