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.

It seems Caddy does not support wildcards/ expression matching in the reverse proxy's header_up.

For example this does not remove any headers:

header_up -X-SHIBBOLETH-*

This works as expected, but is limited in its use:

header_up -X-SHIBBOLETH-LOGIN

It'd be great if Caddy would support wildcards/ expression matching in the reverse proxy's header_up/ header_down.

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.

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

Is your feature request related to a problem?

While setting the target interface's ip should work in most cases, it's possible that multiple devices have the same ip.

Also i'm having trouble using a wireguard vpn when i set Table=off. Table=off disables setting up the routes for the vpn and it justs shows up as a regular device. The connection is fine as pycurl can access it when i set

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

Dec	JAN	Feb
	06
2021	2022	2023

HTTP

Here are 9,699 public repositories matching this topic...

httpie / httpie

psf / requests

caddyserver / caddy

mitmproxy / mitmproxy

aria2 / aria2

curl / curl

dromara / hutool

vapor / vapor

ehang-io / nps

tsenart / vegeta

locustio / locust

go-kratos / kratos

gorilla / mux

hapijs / hapi

julienschmidt / httprouter

uNetworking / uWebSockets

trimstray / nginx-admins-handbook

psf / requests-html

aio-libs / aiohttp

Is your feature request related to a problem?

snail007 / goproxy

http-party / http-server

nock / nock

graphile / postgraphile

sindresorhus / got

go-chi / chi

postmanlabs / httpbin

jeasonlzy / okhttp-OkGo

asciimoo / wuzz

hyperium / hyper

apache / thrift