-
Updated
Nov 26, 2021 - 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 9,525 public repositories matching this topic...
-
Updated
Nov 28, 2021 - C
We had a typo in our code that led to this error: https://github.com/vapor/vapor/blob/main/Sources/Vapor/Routing/Parameters%2BRequire.swift#L23. It was hard to debug in part because of the vague Abort(.internalServerError)
. I suggest adding a reason
value to the Abort
, unless that would be considered a breaking change. I can submit a PR if you're interested.
-
Updated
Nov 9, 2021 - Go
-
Updated
Sep 23, 2021 - Go
-
Updated
Nov 23, 2021 - Python
-
Updated
Nov 28, 2021 - Go
-
Updated
Nov 13, 2021 - JavaScript
-
Updated
Nov 24, 2021 - C++
-
Updated
Oct 20, 2021 - 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
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
-
Updated
Nov 24, 2021 - Go
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
-
Updated
Nov 24, 2021 - TypeScript
-
Updated
Nov 18, 2021 - TypeScript
-
Updated
Nov 18, 2021 - Go
-
Updated
Nov 23, 2021 - C++
It seems Caddy does not support wildcards/ expression matching in the reverse proxy's header_up.
For example this does not remove any headers:
This works as expected, but is limited in its use:
It'd be great if Caddy would support wildcards/ expression matching in the reverse proxy's header_up/ header_down.