stale SigV4 headers sent unintended
Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking state information.
- Обновитесь до 7.81.0-1ubuntu1.30
- Обновитесь до 8.18.0-1ubuntu2.8
- Обновитесь до 8.20.0-2ubuntu11.1
- Обновитесь до 8.22.0-1
- Обновитесь до 8.5.0-2ubuntu10.16