Brew is listed as the recommended way of installing httpie on macOS. However, it doesn't work with auth plugins.

For example, if you pip3 install requests-hawk and then run http --help hawk will not show as an auth type. If you pip3 install httpie-oauth it will install httpie via pip as a dependency and overwrite the brew installed link in /usr/local/bin/http and now all the plugins wil

tldr; in multi-process environment (Celery) sessions might lead to request/responses being mixed up.

It is unsafe to use Session in a multi-process environment - if the fork happens after Session initialisation the underlying connection pool will be shared across both processes, leading to potentially dangerous and hard to debug issues.

I'm not sure what should happen - whather a code change

Go over the Caddy 2 code base at some point and see where we can take advantage of inlining for performance improvements. See: https://blog.filippo.io/efficient-go-apis-with-the-inliner/

I noticed that the advanced installation guide recommends using sudo for installation with pip. This can cause problems because pip and the system package manager disagree on who owns what, and in some cases can actually break the OS.

Instead, I suggest advising to install in a virtualenv, or at least in the user site. I don't have the time now to make a full PR, but here's a suggested wo

From https://tools.ietf.org/html/draft-barnes-tls-pake-04:

"In prior versions of TLS, this functionality has been provided by the integration of the Secure Remote Password PAKE protocol (SRP) [RFC5054]. The specific SRP integration described in RFC 5054 does not immediately extend to TLS 1.3 because it relies on the Client Key Exchange and Server Key Exchange messages, which no longer exist

Description of issue / feature request

Is there any difference between: https://pypi.org/project/locust/ and https://pypi.org/project/locustio/ ?

Also, there is a this conda package: http

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

• Parse out common problems in past issues (middleware, favicons, redirects)
• Update question issue template to link to that section of the README

Context

currently, I found nock and am trying to test out a http module flow. along the way, we require extracting the address() result object.

w/in the response, we have this event:

req.on( 'socket', ( socket ) => {
      console.log(socket);
      req[ '_socketAddr' ] = socket.address();
} );

What are you trying to do and how would you want to do it differ

Add in documentation part (maybe into tutorial) where explaining why all connection, settings and etс, we add to the instance of application.

example:

async def init_pg(app):
    conf = app['config']['postgres']
    engine = await aiopg.sa.create_engine(
        database=conf['database'],
        user=conf['user'],
        password=conf['password'],
        host=conf['host']

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

Test that setting self.resp_options.default_media_type overrides the default media type passed into the falcon.API() and falcon.wsgi.App() initializers.