As mentioned in #3854, Let's Encrypt now provides two different chains when acquiring a certificate: one with a cross-signed root certificate (default) and one with a self-signed root certificate.

I'd like to use the alternative chain, which seems to be possible using the preferred_chains option in Caddy. From what I'v

If you're using proxies with requests-html and rendering JS sites is all good. Once you render a website pyppeteer don't know about this proxies and will expose your IP. This is an undesired behavior when scraping with proxies.

The idea is that whenever someone passes in proxies to the session object or any method call, make pyppeteer also use these proxies. #265

🐣 Is your feature request related to a problem? Please describe.
We had a report in aiohttp-session (see aio-libs/aiohttp-session#574) that a user submitting a 'large' cookie had the cookie dropped by the receiving browser.

According to RFC 6265 - section 6.1:

General-use user agents SHOULD
provide each of the following minimum

As we attempt to pick up the release cadence, we are in need of an explicit changelog file which enumerates changes in each version. This should be a markdown or plaintext file adhering to some form of standardized format. Ideally, it will be able to work with #582.

Context

This isn't really a feature request, as what I need is possible with nock as-is. But I spent several hours searching, reading old issues and searching through the source code to find the solution, so I thought this might help others.

I am testing code that accesses a service that sets the statusMessage of the response, as well as the statusCode. I am using nock to mock the server

As pointed out by @Stargateur in falconry/falcon#1906 (comment), our JSONHandler customization docs could be made clearer by separately illustrating different (albeit closely related) concepts:

• Use a custom JSON library (such as the exemplified rapidjson). Customize para