HTTP

What enhancement would you like to see?
I would like to disable all warnings when using --check-status together with --quiet (that is the behaviour prior to issue #1026 ). It can be implemented as another flag (--quieter or --no-warnings)

What problem does it solve?
I am using a script with some failing scenarios being handled by the return code and I prefer a cleaner output, without

I have modified the default file_server browse template to integrate it with a website, by using httpInclude to load blocks of HTML containing the header, footer and theme. These files are hosted on the same Caddy instance, and it works well provided that compression is not enabled. When compression is enabled, the file_server browser becomes garbage: it appears that raw compressed data is inc

When sending a request body that decodes a Content type. If the request is sent as multipart with the right header set, but the body is empty, a 500 error is returned. This can cause problems with apps that have automatic reporting for internal server errors as it should be reported as a bad request

After PR #1401 merged, many of our sub modules are failing lint, we should fix all of them.

To fix these, take a look at hack/.lintcheck_failures for a list of currently lint failed modules.

You can check a module by removing it from the .lintcheck_failures list and running make fix to auto fix some lint errors.

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

🐞 Describe the bug

TraceConfig.on_response_chunk_received doesn't trace if the response body is read from ClientResponse.content

This behavior isn't obvious when looking at Tracing Reference, [Streaming Response Content](https://docs.aiohttp.org/e

This is a feature request, to display the valid SSL name (from the certificate) when starting up the server.

Steps to reproduce the issue, if applicable. Include the actual command and output and/or stack trace.

$ http-server -S

Starting up http-server, serving ./ through https
Available on:
  https://127.0.0.1:8080
  https://192.168.77.123:8080

**What did you exp

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

At the time of writing, the close() method of resp.stream is only called if the provided generator is successfully exhausted (or yields None).

However, the primary use case of the close() method is freeing up resources, so one might expect the method to be called regardless. It is a