-
Updated
Oct 15, 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,330 public repositories matching this topic...
-
Updated
Oct 17, 2021 - C
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
-
Updated
Oct 15, 2021 - Go
-
Updated
Sep 23, 2021 - Go
-
Updated
Oct 13, 2021 - Python
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.
-
Updated
Oct 12, 2021 - JavaScript
-
Updated
Oct 7, 2021 - C++
-
Updated
Oct 1, 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
Sep 28, 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
Oct 11, 2021 - TypeScript
-
Updated
Oct 15, 2021 - TypeScript
-
Updated
Oct 10, 2021 - Go
-
Updated
Oct 16, 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.