-
Updated
Dec 2, 2020 - Python
HTTP
HTTP (Hypertext Transfer Protocol) is a request and response protocol used to send a request to a server and receive a response back in the form of a file. HTTP is the basis of data communication for the web. HTTPS is an evolution in HTTP, where the “S” stands for secure socket layer allowing communication in HTTP to be more secure.
Here are 7,991 public repositories matching this topic...
-
Updated
Dec 17, 2020 - C
-
Updated
Nov 23, 2020 - Go
-
Updated
Oct 24, 2020 - Go
-
Updated
Dec 17, 2020 - Python
-
Updated
Dec 4, 2020 - JavaScript
-
Updated
Dec 11, 2020 - C++
-
Updated
Nov 17, 2020 - Shell
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
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
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
Add a changelog
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.
-
Updated
Dec 11, 2020 - TypeScript
-
Updated
Dec 11, 2020 - Go
-
Updated
Dec 17, 2020 - TypeScript
-
Updated
Dec 11, 2020 - Go
The 3.0 ASGI implementation already affords long-polling, but it would be useful to provide a recipe to demonstrate the pattern in the context of a Falcon app.
Also, for the sake of efficiency, we may want to provide a req.wait_disconnect() or similar method that can be executed in a background task within a responder. The responder could then use this in order to detect if it should abandon
-
Updated
Nov 18, 2020 - Go
-
Updated
Oct 20, 2020 - Python
I am trying to build a Caddy configuration that can cater to multiple environments (production, staging, local development).
To achieve this, I want to use environment variables for the base host names/urls, via the
{env.*}placeholder. This works great in addresses, route matches and upstream reverse-proxy configuration.Unfortunately, using the same approach does currently not work when