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.

Caddy version: v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A=

I am trying to pass pem-encoded client certificate to proxied service via a X-SSL-Cert header, like so:

sub.example.com {
    reverse_proxy 127.0.0.1:8000 {
        header_up X-SSL-Cert {http.request.tls.client.certificate_pem}
    }

    tls {
        client_auth {
            mode require
        }
    }
}

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

Long story short

I've been using low-level machinery exposed by aiohttp for my framework.
When I learned about handle_signals=True I started testing it and it turned out that my process always exited with return code 1 on SIGTERM and SIGINT.

This was confusing and I thought that it's a bug. But then, after diving into the code deeper, I realized that with this option enabled, aioht

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

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.

The example nginx configuration in the Deploying Falcon on Linux with NGINX and uWSGI article could probably be improved to include https configuration and redirect of http to https, since I believe it's the most common configuration now.

Maybe we could use a configuration from this great [Mozilla site](https://ssl-config

Sep	OCT	Nov
	27
2019	2020	2021

HTTP

Here are 7,760 public repositories matching this topic...

httpie / httpie

psf / requests

caddyserver / caddy

aria2 / aria2

mitmproxy / mitmproxy

curl / curl

looly / hutool

tsenart / vegeta

ehang-io / nps

locustio / locust

gorilla / mux

hapijs / hapi

julienschmidt / httprouter

uNetworking / uWebSockets

trimstray / nginx-admins-handbook

psf / requests-html

aio-libs / aiohttp

Long story short

jeasonlzy / okhttp-OkGo

nock / nock

http-party / http-server

graphile / postgraphile

snail007 / goproxy

postmanlabs / httpbin

asciimoo / wuzz

sindresorhus / got

go-chi / chi

falconry / falcon

apex / up

httpie / http-prompt

apache / thrift

Essential cookies

Always active

Analytics cookies