对于使用云服务的负载均衡器（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/

• 是否试过最新的版本 (https://github.com/XX-net/XX-Net/releases )？

• 是否查看过 Wiki (https://github.com/XX-net/XX-Net/wiki )？

• 是否以相关关键词搜索过类似 issues？

• 描述遇到的问题，贴出所有能帮助分析问题的状态页和日志，如包含大量文本时，请上传为 txt 文件：

• 如果问题得到解决，请务必回复相关情况，谢谢。

XX-Net Status:

sys-platform: x86_64, Darwin-18.2.0-x86_64-i386-64bit
os-system: Darwin
os-version: Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018;

Is your feature request related to a problem? Please describe.
The {{< highlight none >}} :~q:foo:bar {{< / highlight >}} blocks don't work on GitHub. It's confusing and makes the code examples almost useless on GitHub itself. And also in your code editor if you have Markdown syntax highlighting with embedded highlighting for nested code.

Describe the solution you'd like

It'd be ne

###GoAgent限制：

• GAE出口IP被定义为“开放代理”
  部分网站屏蔽GAE的IP访问，或将其视为不信任。
  无法使用GAE的IP对维基百科进行匿名编辑。

• Facebook 上传文件：图片/视频等
  原因: Facebook上传文件，采用HTTP OPTIONS指令，不在GAE的支持范围
  解决方法：访问https://upload.facebook.com/，再次尝试。也可以访问手机域名https://m.facebook.com/上传。

• Twitter上传大文件/图片
  GoAgent 对上传超过64k的数据存在问题
  GAE的限制是10M
  因此有可能解决，还有待研究

The background image on the website doesn't look that great (due to high jpeg compression) and doesn't tile properly on large screens.

Here's a better way: http://qrohlf.com/trianglify/

How to let server in ubuntu print log?

suggest： Output specific logs when be scanned, record the scanner's IP，use fail2ban ban scanner ip.

Prerequisites

• Did you check the wiki?
• Did you search in issues?
• Are you running the latest version?
• I will write this according to

Here's the output in Terminal:

Here's the analogous output in the hotel's browser view:

<img width="823" alt="Screen Shot 2019-07-27 at 5 43 59 PM" src="https://user-images.githubusercontent.com/22218/62000853-af0da200-b096-11

I don't know chinese but is there any english docs?

https://wproxy.org/whistle/

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

toxiproxy-cli h t

gives me an incorrect example for adding new toxic:

toxic add:
usage: toxiproxy-cli add --type --toxicName
--attribute <key=value> --upstream --downstream

example: toxiproxy-cli toxic add myProxy -t latency -n myToxic -a latency=100,jitter=50

This leads to:

Failed to add toxic: AddToxic: HTTP 409: toxic alre

We need a space to put settings (e.g. port number, reverse proxy options) and other stuff (root certificate download button, link to github, license info, etc.). The plan is to show the tab bar back again and create a new, custom tab with Settings/About.

<img width="197" alt="screen shot 2016-03-15 at 11 01 55" src="https://cloud.githubusercontent.com/assets/985504/13774120/81896dc2-ea9d-11e5-927

你好,我按照Readme配置好了server端,也成功的启动了, 但是登陆成功之后,直接又闪退回登陆界面.想问下是怎么回事. 具体操作我录了一个gif图片 如下.
http://linuxsogood.org/wp-content/uploads/2017/09/proxy.gif

github试了好几次都传不上来图片,所以放我个人博客了.
下面是日志.

`2017-09-11 03:17:54,741 INFO [org.fengfei.lanproxy.server.config.web.routes.RouteConfig] - <handle request for api /login>
2017-09-11 03:27:05,003 INFO [org.fengfei.lanproxy.server.config.web.routes.RouteConfig]

As it currently stands, the deferred initialization of a ghost object (as per documentation) looks quite messy:

$initializer = function (
    \ProxyManager\Proxy\GhostObjectInterface $ghostObject,
    string $method,
    array $parameters,
 

Is your feature request related to a problem? Please describe.

Not related to a problem

Describe the solution you'd like

We opened #808 to discuss how we might use GitHub actions. At the time, this repo didn't have actions enabled. Now that it does, we should try them out for some of the things in that thread.

_Edit from @arschles - we have focused this issue to just the twitte

Right now we emit a message like

T: Error: Unable to find cluster information
T: No current-context set. Please use the --context option to 
T: explicitly set the context.

This is all fine, but some higher-level explanation would be helpful as well, probably linking to documentation:

T: Telepresence uses kubectl/oc to access your Kubernetes/OpenShift
T: cluster. Ple