Request time out will kill the process!

项目中前台所有的调用接口都是相同的URL，是post的，只是在post中有一个标识参数，根据这个不同的参数来返回不同的东西，我如果在前台用URL映射的话就有问题了，nproxy能不能根据post的参数来映射到不同的文件去

目前不支持对线上服务的combo地址解析.配置规则无效

For some projects, static files url will be appended a version control flag like dev-SNAPSHOT or production number. Actually, in source css file, it just use the original image, the url of which doesn't contain flags. Like following:

src: image/a.png

production:  image/a-version.png

So, proxy should support such case

访问https的地址时，报告"网站的安全证书不受信任！", 能否避免出现这种警告

pattern: 'homepage/ui/img'

some images with url http://localhost:8080/ss/dd/homepage/ui/img/sss_dev-snapshot.png would not found in local

Hello,
I'm trying to use nproxy behind a corporate firewall with a proxy of it own. Does nproxy support upstream proxies? Will it apply env.http_proxy to the request agent like the request module?

原来请求的页面的header中有Access-Control-Allow-Origin，但是使用nproxy后response的header中没有Access-Control-Allow-Origin了？

getting an error on the console output from nproxy after a matched url: [ERROR] uncaughtException: mime.lookup is not a function

Mac os 10.12.4
chrome 67
node v8.10.0

RT. 问题我也在排查

这个标题看起来有点拗口。我说一下前因后果。

第一步，我在本地起了一个基于 Node 的 HTTP 服务，主要目的是实现本地的 Stylus 编译，通过中间件实现透明自动编译（其实这里的 Stylus 不重要，因为我去掉 Stylus 的部分并不影响最终结果）。主要示意代码如下：

var dir = '/my/local/path'
var app = connect()
app
//  .use(
//      stylus.middleware({
//          src: dir,
//          dest: dir,
//          compile: compile
//      })
//  )
    .use(
        connect.static(dir)
    )
    .listen(3006)

第二步，我为 nproxy 设定中转规则：

{
    pattern: /http:\/\/www\.sample\.com\/(.+)/,
    responder: 'http://127.0.0.1:3006/$1'
}

第三步，在浏览器中通过 nproxy 去访问 http://www.sample.com/path/to/test.js 这个资源（我们期望的结果是浏览器得到 http://127.0.0.1:3006/path/to/test.js 内容）。

在首次访问时可以得到正确的响应，但刷新浏览器（Cmd + R）再次请求时，只会得到空白的结果。（请原谅我暂时还没有分析出确切的状况是否响应体丢失、响应体为空、响应头有问题等。）

如果强制刷新（Cmd + Shift + R）则可以得到正确的响应。如果直接访问 http://127.0.0.1:3006/path/to/test.js 则总是可以得到正确的响应。

在我测到的所有浏览器（Firefox、Chrome、iOS Safari、Android Chrome）上均存在此现象。

系统环境：

• Mac OS X v10.8.5
• Node v0.10.26
• nproxy v1.4.3
• connect v2.25.7
• Firefox v31
• Chrome v36

Since the default request timeout is 5 seconds, the forward requests to a slow server are always timeout.

dynamically reload configuration file without restarting nproxy server

responder

directory match should support any type of file. Now directory match just supports image match.

看的文档还是不明白https的请求如何用nproxy做代理

我配置了http代理，其他网站就访问不了了，所以我想这个代理应该生效了；

我安装了nproxy，运行nproxy -V可以拿到版本号1.4.5，所以我猜nproxy的安装应该没有问题；

我运行 nproxy -l code/cellar/web/articles/nproxy/config.js，nproxy也启动了，我的config文件内容是这样：

module.exports = [
    {
        pattern: 'a.js',
        responder:  "/Users/zhaoxiaoqiang/code/cellar/web/b.js"
    }
];

然后我再本地启动了一个网站，访问a.js，发现无法访问，关闭代理可以访问，谁能告诉我这是怎么回事？哪里错了吗？（代理的被动模式开和不开一个样）

该证书因为其自签名而不被信任。
该证书仅对 goddy 有效。
证书过期日期为 2012/9/17 12:15。
而当前日期为 2015/8/19 14:15。

（错误码： sec_error_unknown_issuer）

TypeError: first argument must be a string or Buffer
    at ClientRequest.OutgoingMessage.write (http.js:768:11)
    at Object.utils.request (/opt/node-v0.10.4/lib/node_modules/nproxy/lib/utils.js:142:15)
    at Object.respondFromWebFile (/opt/node-v0.10.4/lib/node_modules/nproxy/lib/middlewares/responders/web-file.js:4:10)
    at Object.respond [as handle] (/opt/node-v0.10.4/lib/node_modules/nproxy/lib/middlewares/respond.js:72:24)
    at next (/opt/node-v0.10.4/lib/node_modules/nproxy/node_modules/connect/lib/proto.js:190:15)
    at Function.app.handle (/opt/node-v0.10.4/lib/node_modules/nproxy/node_modules/connect/lib/proto.js:198:3)
    at app (/opt/node-v0.10.4/lib/node_modules/nproxy/node_modules/connect/lib/connect.js:65:37)
    at Server.<anonymous> (/opt/node-v0.10.4/lib/node_modules/nproxy/lib/nproxy.js:49:5)
    at Server.EventEmitter.emit (events.js:98:17)
    at HTTPParser.parser.onIncoming (http.js:2015:12)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:119:23)

错误发生在使用POST提交表单时，我看了下代码

/opt/node-v0.10.4/lib/node_modules/nproxy/lib/utils.js:47

  /**
   * Simple wrapper for the default http.request
   *
   * @param {Object} options options about url, method and headers
   * @param {Function} callback callback to handle the response object
   */
  request: function(options, callback){
    //.......
    if(requestMethod === 'POST'){
      request.write(options.data);
    }
    //.......
  }

调用来源于/opt/node-v0.10.4/lib/node_modules/nproxy/lib/middlewares/responders/web-file.js:4

var utils = require('../../utils');

function respondFromWebFile(filePath, req, res, next){
   utils.request({
      url: filePath,
      method: req.method,
      headers: req.headers
    }, function(err, data, proxyRes){
      if(err){ throw err; }
      res.writeHead(200, proxyRes.headers);
      res.write(data);
      res.end();

    });
};

module.exports = respondFromWebFile;

对于POST请求没有传data

Hi @goddyZhao ，因为网站启用了 HSTS，用户不能忽略浏览器警告继续访问网站，这种情况怎么解决呢？是不是需要 nproxy 生成一个证书，然后设置信任？

我有看到 Charles 是这样处理的：http://www.charlesproxy.com/documentation/proxying/ssl-proxying/

功能很好，非常感谢！只是有个奇怪现象

比如刷新 http://localhost/demo/qnecrm/

nproxy会打印错误日志

[ERROR] Request timeout for http://www.flvcd.com/parse.php?flag=&format=&kw=http://localhost/demo/qnecrm/
[ERROR] url: http://www.flvcd.com/parse.php?flag=&format=&kw=http://localhost/demo/qnecrm/
[ERROR] msg: socket hang up

这是为什么呢

机器是mac chrome
@goddyZhao

哈哈，希望这个可以增强下。
当多条规则匹配时，如果实际想匹配的是第二条，但是第一条却匹配了（发现匹配即中止查找），响应替换表达式却找不到该路径(实际上的期望值该是第二条替换)，在控制台的打印信息中实际上是第一条出错？（用户的潜意识是第二条配置出错了!）
建议：
一：报错情况下 控制台输出pattern或输出实际的responder路径（比如期望值是patternB: X:/file/b.js,但实际上因为规则写的有问题，替换的patternA: X:/file/a.js）

二：嘿嘿。这种需求不知是否广泛(combo的某种形式)。
http://a.b.c/??后跟的文件动态的，或者可能有多重组合，如果为每条匹配情况写一条规则稍显蛋疼.可以这样的话就好了,类似：
{
pattern: /(?=-min)/g,
responder:{
dir: 'x:\aaa\bbb',
src: '$1' //某种形式的分组全部匹配，自动转化成数组
}
}

不支持 Rest API

RT,执行nproxy提示command not found

pattern: /pattern/ => pattern: 'pattern'

module.exports = [
    {
        parttern: \http\:\/\/test\.com\/hxm\,
        responder: "http://test.com:9000/hxm"
    }
];

我想通过这个对某个域做端口映射 但是没成功

比如我测试时把文件替换成：http://s1.bdstatic.com/r/www/cache/static/global/js/home_f949edf5.js

返回文件内容405 Not Allowed/403 Forbidden，使用浏览器直接访问地址是正常的。

NProxy should add/change/remove some http response headers to make it uncached in the browsers, just like what Fiddler does.

For example,

Fiddler will replace such http response headers:

Cache-Control: public
Expires: Sat, 21 Oct 2023 19:18:19 GMT

to

Cache-Control: max-age=0, must-revalidate

我在使用的时候发现，websocket的请求都是timeout,然后提示msg: socket hang up，如何来设置相关配置，让socket能正常使用呢？

Hello!

I have been working on my own development proxy (https://github.com/fabiosantoscode/magicProxy) for a while now. I did not know of your proxy when I started. I just created it because I had to work on someone else's site and didn't want to have to install the whole thing locally.

My own project uses node-http-proxy, an existing proxy project, as its backend, has a flaky plugin system and includes some plugins which do file replacement like nproxy does, and some which do HTML transforms. One of them uses node-trumpet to change anything with [src] and [href] attributes, and the other uses cheerio to manipulate the DOM before it gets to the browser.

The roadmap of the project includes https://github.com/fabiosantoscode/letmeshowyoutheworldthroughmyeyes (I've opened this repo today), which should allow a developer to share his proxied view with a client or co-worker.

Seeing that we have interesting stuff cooking in different fronts, and have projects similar in a lot of things, why not join forces?

Join the two projects into one, work together on that, and get the best of both worlds. The cool configurability of this project, plus DOM manipulation plugins and shareability through letmeshowyoutheworldthroughmyeyes (although that project should be pretty much proxy agnostic).

To be clear, I intend to shutdown magicProxy and start porting its stuff over to this one.

What do you say?

Don't support Rest API

npm install nproxy -g
nproxy
[INFO] NProxy started on 8989!
[INFO] connect to https server successfully!
[ERROR] url: /
[ERROR] msg: connect ECONNREFUSED
[INFO] connect to https server successfully!
[ERROR] socket error read ECONNRESET

Windows 7

所有浏览器均打不开HTTPS网址，显示404

似乎是重定向到127.0.0.1

如果我本地127.0.0.1开了80端口，就会从80端口上获取结果，关了80则显示404

可以拿支付宝网址测试：https://www.alipay.com/

Support such replacement:

pattern: '?://[\w.](?::\d+)?/ui/(.)_(?:[0-9a-f]{32}|dev-snapshot).(\w+),
responder: 'D:\jboss-eap-4.3\server\main\deploy\main-sfv4.ear\sfv4.war\ui$1_dev-snapshot.$2'

It is not an issue. Good job! 👍

It is not so fast for proxying https request in homepage

看到之前有修复过PUT的bug，今天在项目中使用DELETE时，发现不能正常工作，代码修改如下后可以工作：

isContainBodyData: function(method){
    if (!method){
      return false;
    }

    var white_list = ['POST', 'PUT','DELETE'];
    return white_list.some(function(i){
      return i === method;
    });
  }

试着增加了DELETE，请作者看下此处是否应增加更多的method支持？

代理时，我是配置的本地相对路径的文件。
代理配置文件和要代理的文件放到同一目录下。配置文件中就直接配置文件名了，但代理时报错说不是一个可用的路径

具体报错信息：
[INFO] matched url: http://xxx/a.js
[ERROR] ENOENT, stat '/dist/a.js'for (http://xxx/a.js) then directly forward it!

本地文件是绝对路径，nproxy的配置文件和a.js在同一个目录

For some url like:

http://host:port/js/a_devsnap-shot.js
http://host:port/js/a_12345556.js

User can define rule to make NProxy ignore the fingerprint which will make possible to replace it with local files that have no such fingerprints.

类似于http://test.com/test.js?v=20160412的文件不能匹配

Goddy, Does it support the Mobile device Proxy?
it is necessary for mobile development

and do you know who I am? :)

pattern = typeof originalPattern === 'string' ? new RegExp(originalPattern) : originalPattern;

originalPattern做为正则的参数，需要把字符串中如 ./这些字符转义处理