Currently the install_trust option for CAs from the pki module can only be configured via JSON/API.

Setting TLS to internal with option on_demand is easily possible with a Caddyfile and allows for a quick and simple internal setup. Trust store installation on the machine itself is not necessary and only leads to startup errors being logged from both sudo and caddy.

Therefore it w

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

👋 THIS IS A GOOD FIRST ISSUE

🐞 Describe the bug

I noticed that the docs have some RST references to internal and external intersphinx objects. We should fix those and enable nitpicky = True by default.

P.S. It is okay to send small PRs to fix references gradually

💡 To Reproduce

Unco

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.

Tests case:

nock('https://xxxx.com').get('/').times(1).reply(200, { mock: 1 });

// first times: print { mock: 1 }
// second and third times: throw error `Nock: No match for request`
for (let i = 0; i < 3; i++) {
  const {data} = await axios({
    url: 'https://xxxx.com/',
    method: 'GET',
  });
  console.log(data);
}

In [README](https://github.com/nock/nock#repeat-response

falcon.uri.encode_value says:

An escaped version of uri, where all disallowed characters have been percent-encoded.

However, it seems that the percent character itself is not encoded...

Cf

>>> from urllib.parse import quote
>>> from falcon import uri
>>> quote('%26')
'%2526'
>>> uri.encode