Upgrade node-http-proxy to 0.10.1.

Intentionally not choosing 0.10.2, which has a websocket proxying Node 0.10
semi-fix which I found to sometimes corrupt data (on Node 0.10). See my analysis
on https://github.com/nodejitsu/node-http-proxy/pull/402

I do not know whether or not the PR corrupts data on 0.8, but it isn't necessary
there, so I'm going to hold off on taking that change until the promised future
complete rewrite of http-proxy to use the new 0.10 streams API.
This commit is contained in:
David Glasser
2013-05-28 14:15:31 -07:00
parent e43f873f6b
commit 75149b75f3
3 changed files with 5 additions and 3 deletions

View File

@@ -17,7 +17,9 @@
* Fix Mongo queries which nested JavaScript RegExp objects inside `$or`. #1089
* Upgrade Underscore from 1.4.2 to 1.4.4.
* Upgrade Underscore from 1.4.2 to 1.4.4. #776
* Upgrade http-proxy from 0.8.5 to 0.10.1. #513
* Upgrade Connect from 1.9.2 to 2.7.10.

2
meteor
View File

@@ -1,6 +1,6 @@
#!/bin/bash
BUNDLE_VERSION=0.3.5
BUNDLE_VERSION=0.3.6
# OS Check. Put here because here is where we download the precompiled
# bundles that are arch specific.

View File

@@ -103,7 +103,7 @@ npm install clean-css@0.8.3
npm install useragent@2.0.1
npm install request@2.12.0
npm install keypress@0.1.0
npm install http-proxy@0.8.5
npm install http-proxy@0.10.1 # not 0.10.2, which contains a sketchy websocket change
npm install underscore@1.4.4
npm install fstream@0.1.21
npm install tar@0.1.14