Scrapy-zyte-smartproxy

Latest version: v2.4.0

Safety actively analyzes 707299 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 4

2.4.0

-------------------

Removed official support for Python 3.4, 3.5, 3.6, 3.7 and 3.8. Added official
Python 3.13 support.

`Backward-compatible
<https://docs.zyte.com/zyte-api/migration/zyte/smartproxy.html#spm-migrate-map>`__
``X-Crawlera``-prefixed headers are no longer translated into their matching
`Zyte API proxy mode headers
<https://docs.zyte.com/zyte-api/usage/proxy-mode.html#zapi-proxy-headers>`_,
Zyte API now handles their translation on the server side.

Added a new ``ZYTE_SMARTPROXY_KEEP_HEADERS`` setting that allows disabling
header dropping and translation.

2.3.5

-------------------

Ban and throttling responses from `Zyte API`_ `proxy mode`_ are now handled in
line with matching responses from Zyte Smart Proxy Manager.

2.3.4

-------------------

`Zyte API`_ `proxy mode`_ now has its own stat prefix.

Some user-facing messages mentioning only Zyte Smart Proxy Manager have also
been updated to reflect the fact that scrapy-zyte-smartproxy also supports Zyte
API proxy mode.

2.3.3

-------------------

Fix response handling for `Zyte API`_ `proxy mode`_. Before, a single
connection issue during a request would add a 90 second delay between requests
until the end of the crawl, instead of removing the delay after the first
successful response.

2.3.2

-------------------

Detect scenarios where the ``proxy`` ``Request.meta`` key has probably been
accidentally copied from an earlier response, warn about it, and fix the value.

The ``Zyte-Client`` header is again sent when using `Zyte API`_ `proxy mode`_,
now that Zyte API supports it.

2.3.1

-------------------

Fixed `Zyte API`_ `proxy mode`_ support by removing the mapping of unsupported
headers ``Zyte-Client`` and ``Zyte-No-Bancheck``.

Page 1 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.