对于使用云服务的负载均衡器（Azure 或者 Google cloud）以及 CDN 的用户，因为负载均衡器和 CDN 是可以直接接管证书和 TSL 甚至 HTTP/2 、 QUIC 的，所以希望 v2ray 作为客户端使用时也能够支持像浏览器一样自动协商底层传输协议是 HTTP 1.1 还是 HTTP/2 或 QUIC 。相当于在入站协议上提供一个尽量简单、不占资源的 HTTP 类型的底层传输协议，如 #1644 所需求的，再由客户端在出站协议上与负载均衡器自动协商。当然如果入站协议也能够提供一个支持多版本协商的 HTTP 底层传输协议那也再好不过。
以及目前 WebSocket 是直接使用 WebSocket 连接的，与浏览器的 HTTP 协商升级为 ws 的行为有所不同，跟据[谷歌云的表述](https://cloud.google.com/load-balancing/docs/

The example code does not work as intended.

Steps to reproduce

Use the example code:

var express = require('express');
var proxy = require('http-proxy-middleware');

var app = express();

app.use(
  '/api',
  proxy({ target: 'http://www.example.org', changeOrigin: true })
);
app.listen(3000);

Expected behavior

This should create a proxy for /api to `http

Most of the headings on the website have anchor link targets, but it's awkward to actually get a link to them. Add anchor.js or something equivalent so there is clickable page element that can be used to obtain a link to an anchored element.

I am looking for examples for defining ingress resources for skipper.
Beside the following documentation, where can I get more examples?

For instance, how would you create ingress resources for the following routes:
path1: * -> "https://www.example.org";
path2: Path("/home") -> "https://www.google.com";
dynamicPath1: Path

On this gif ( https://raw.githubusercontent.com/constverum/ProxyBroker/master/docs/source/_static/cli_serve_example.gif ) the server prints an info line when a client connects.

The current version doesn't do that, though it would be very useful. I tried the command that is on the GIF.

User story.
As a developer, I can change a referenced example file, so that I can see the changes after a request to prism.

Is your feature request related to a problem?
Prism only watches the spec file for changes and even if it changes, it doesn't reload referenced examples. This is useful because spec files can get extremely big so $ref usage is a must to keep it manageable.

asyncsrc noted in #351 that HSTS errors could be avoided if certificates are imported into the system keychain.
We should perhaps have OS-specific and/or browser-specific docs on importing certificates

like SOZU_CONFIG, SOZU_BIN would fix a path at compile time: the location of the executable

Right now there aren't any instructions in the README.

Currently there is no reference implementation of the keyserver in this code base. We should provide one. Here is the API.

Ideally we also provide a gRPC and OpenAPI/swagger doc for this API as well.

transformRequest only fires if its a method that can have a body. This is misleading, as it's very common to perhaps want to tweak headers or something on an outgoing request before it gets to the destination server.

The solution is "use" instead of "transformRequest", but I was banging my head on this today.