Proxy Saver Protocols

The Proxy Saver supports all standard and modern proxy protocols, ensuring compatibility with any browser or web scraping tool. Below are the details and specificities of each protocol's usage.

While all the provided examples account for the possibility that the Proxy Saver certificates may not be properly installed, the recommended approach is to configure them correctly rather than bypassing SSL errors.

HTTP

HTTP is the simplest proxy protocol and is universally compatible with all browsers and libraries.
Below are some examples:

HTTPS / HTTP2

Using HTTP as a proxy protocol is straightforward, but opting for HTTPS ensures that your credentials are securely encrypted from the very start of the CONNECT phase.

By default, curl will use HTTP/1.1 over TLS unless you have a recent version that supports HTTP/2 and explicitly specify the necessary flags. Chrome, on the other hand, defaults to HTTP/2 but will gracefully downgrade to HTTP/1.1 over TLS if needed.

The Proxy Saver natively supports HTTP/2 while also maintaining compatibility with HTTP/1.1 over TLS to accommodate the broadest range of browser implementations.

SOCKS5

Socks5/h is another popular protocol used for HTTP proxying

Socks5 auth mechanism

For browsers and libraries that support native SOCKS5 authentication, the Proxy Saver does as well, ensuring seamless integration.

However, not all browsers support this mechanism.

While Chrome and Chromium do not support the SOCKS5 authentication mechanism (and have no plans to), Scrapfly offers a reliable workaround.

For browsers and libraries that do not support SOCKS5 authentication natively, Scrapfly offers a simple workaround using a custom header.
Simply include your authentication string in the X-SAVER-AUTH header.
This custom authentication mechanism enables the use of the SOCKS5 protocol with any library that supports it.

Below are some usage examples: