archive-gh-me/node-http-proxy
1
0
Fork 0
mirror of https://github.com/http-party/node-http-proxy.git synced 2025-12-08 20:59:18 +00:00
Code Issues Projects Releases Wiki Activity
514 Commits 34 Branches 97 Tags
Commit Graph

224 Commits

Author SHA1 Message Date
indexzero
3130665d9f [fix] Emit notFound event when ProxyTable location does not exist. Fixes #355. Fixes #333. 2013-03-09 02:29:58 -05:00
indexzero
4c1a2c1416 [fix] Make options immutable in RoutingProxy. Fixes #248. 2013-03-09 02:21:31 -05:00
colinmollenhour
b1c4bd61e8 Remove data event that is not needed after-all. 2013-03-09 01:48:42 -05:00
Colin Mollenhour
3b86a7aae3 Add 'proxyResponse' event so observer can modify response headers or abort response. 2013-03-09 01:48:37 -05:00
Colin Mollenhour
4c130f5dac Allow event observers to access upstream response headers and data. 2013-03-09 01:48:29 -05:00
indexzero
9cecd97153 [minor] s/function(/function (/ s/){/) {/ 2013-03-09 01:43:25 -05:00
jpetazzo
ba65a485fc Fix typo which slipped in during patch clean-up 2013-03-09 01:21:30 -05:00
jpetazzo
ef66833c4d Fix truncated chunked responses 2013-03-09 01:21:21 -05:00
Charlie Robbins
af9eb06e47 Merge pull request #298 from Kami/connection_keep_alive_on_1_1 
If HTTP 1.1 is used and backend doesn't return 'Connection' header, expicitly  return Connection: keep-alive.
 2013-03-08 22:11:37 -08:00
indexzero
28a3b0a6f0 [fix] Remove special case handling of 304 responses since it was fixed in 182dcd3. Fixes #322. 2013-03-09 01:10:02 -05:00
Yosef Dinerstein
ffe74ed299 - support unix donain sockets and windows named pipes (socketPath) on node 0.8.x. On node 0.6.x the support was opaque via port, but on the new node, socketPath should be set explicitely. 
- avoid adding multiple headers with the same name
- fix bug in setting connection
 2013-03-09 01:05:22 -05:00
indexzero
c6da760ca9 Revert "[fix minor] Prevent crashes from attempting to remove listeners more than once when proxying websocket requests." 
This reverts commit a681493371ae63f026e869bf58b6fea682dc5de3.
 2013-03-09 00:43:25 -05:00
indexzero
a681493371 [fix minor] Prevent crashes from attempting to remove listeners more than once when proxying websocket requests. 2013-03-09 00:40:00 -05:00
unknown
2055d0c8ec memory leak fix in closing of the scokets 2013-03-09 00:36:19 -05:00
indexzero
013cb2e0c2 [fix] Ensure response.headers.location is defined. Fixes #276. 2013-03-09 00:28:50 -05:00
Otávio Ribeiro
9672b99271 cleanning 2013-03-09 00:20:46 -05:00
Otávio Ribeiro
8d8739999f cleanning 2013-03-09 00:20:42 -05:00
Otávio Ribeiro
31fc94aa5e working on x-forwarded-for 2013-03-09 00:20:38 -05:00
Otávio Ribeiro
133240937d working on x-forwarded-for 2013-03-09 00:20:33 -05:00
Otávio Ribeiro
916d44e3d2 Routing Proxy was not sending x-forward-*. Fixing It... 2013-03-09 00:20:26 -05:00
Charlie Robbins
025adc2912 Merge pull request #365 from adjohnson916/master 
routing proxy 'this' reference bug?
 2013-03-08 21:14:14 -08:00
Giannis Dzegoutanis
3b84e27ab4 remove offending code, final fix for issue #364 2013-02-12 20:43:22 +01:00
Giannis Dzegoutanis
43e5f33320 fixed issue #364 'proxyError' event emitted twice 2013-02-10 23:07:40 +01:00
Anders Johnson
15afc23a27 fix 'this' reference in routing proxy listener bindings 2013-01-12 21:55:46 -06:00
Maciej Małecki
223eacda85 [fix] Don't remove error listener after response ends 
In some rare cases, `error` event might still be emitted after the
response has ended. This is (most likely) a bug in the `node` core.
 2012-12-23 00:44:21 +01:00
Maciej Małecki
edfe869159 [fix] Handle errors on request object 
Sometimes a request emits `error` event with a `Parse Error`.
 2012-12-21 20:56:01 +01:00
Maciej Małecki
2a61ec85bd [fix] Handle socket errors 2012-12-13 00:02:54 +01:00
Fedor Indutny
0fd5884a0f http-proxy: 304 responses should emit 'end' too 2012-11-21 12:21:55 +04:00
Colton Baker
8a88774ecf [fix] Convert strings to numbers if possible in .createServer 
Fixes #321
 2012-11-06 17:47:47 -05:00
Fedor Indutny
a487dc9b58 lib: allow overriding maxSockets 2012-10-26 01:39:13 +04:00
Fedor Indutny
5df6e7bdb8 http-proxy: emit websocket:start 
* routing-proxy: allow listening for websocket:* event
 2012-10-23 23:54:23 +04:00
Maciej Małecki
eafdc744b6 [refactor] Pass all options to Agent constructor 2012-09-27 10:00:10 +02:00
Bradley Meck
698b01da8e [fix] spdy should look like https when forwarding (until we get a client) 2012-09-20 10:54:29 -05:00
Tomaz Muraus
850171cdc4 If HTTP 1.1 is used and backend doesn't return 'Connection' header, explicitly 
return Connection: keep-alive.
 2012-08-16 21:47:56 -07:00
Maciej Małecki
cee27feedd [minor doc] Correct comment 2012-08-10 21:45:30 +02:00
Maciej Małecki
812868ddfc [minor] Remove setEncoding on incoming socket 
This isn't needed as we don't do any string operations and `setEncoding`
results in a higher memory usage and is slower.
 2012-08-10 21:43:55 +02:00
Wesley Mason
89459bfd32 If supplied pass changeOrigin option through to HttpProxy instance if set in RoutingProxy 2012-07-25 14:17:48 +01:00
Bert Belder
24b84068ea Fix socket leaks when FIN packet isn't responded to 2012-07-24 23:05:04 +02:00
Maciej Małecki
0d00b06af3 [fix] destroy() websockets in case of an error 
Not doing so caused websockets in `CLOSE_WAIT` to pile up and cause
proxy to exceed open file descriptor limit.
 2012-07-24 16:30:51 +02:00
indexzero
36226daa2e [dist] Complete JSHint compliance except for too many var statements 2012-07-22 03:14:01 -04:00
indexzero
4999b20b84 Merge branch '0.8.2' 2012-07-22 02:49:43 -04:00
Charlie Robbins
02b914d609 Merge pull request #246 from tellnes/proxy-remove 
Implement RoutingProxy.prototype.remove
 2012-07-21 23:33:07 -07:00
Charlie Robbins
f28c62c815 Merge pull request #235 from Filirom1/patch-1 
prefer `target.hostname` over `target.host`
 2012-07-21 23:31:35 -07:00
Christian Howe
0273958b0a Use changeOrigin for proxyRequest. 2012-07-22 02:24:15 -04:00
Christian Howe
04ce49c5b2 Whitespace fixes. 2012-07-22 02:24:02 -04:00
indexzero
55286a7c49 [fix api] Optimize lookups in the ProxyTable. Ensure that RoutingProxy can proxy to https by default. 2012-07-22 01:02:51 -04:00
Ramprasad Rajendran
0933f1c598 Fix bug: x-forwarded-proto set incorrectly 
When routed via multiple proxies, x_forwarded_proto set as httphttps or
wswss instead of http,https or ws,wss, since + operator seems to have a
higher precedence than the terniary operator and the expression was
getting evaluated to true always
 2012-06-19 12:00:24 +05:30
Christian Howe
64c974755d Merge pull request #218 from CodeRarity/proxy-table-fix 
Fix problem with req.url not being not properly replaced.
 2012-06-05 13:04:18 -07:00
Ryan Stevens
ca37ad7436 [fix] x-forwarded-proto sets properly 
The ternary was evaluating truthy for "," + req.connection.pair which is always true because its always a non empty string.  Wrapped actual condition to properly concatenate the product of the ternary.  let me know if you prefer the style   (req.connection.pair ? 'https' : 'http')

https://github.com/nodejitsu/node-http-proxy/issues/250
 2012-05-22 12:54:47 -07:00
Christian Tellnes
0532995dfa Implement RoutingProxy.prototype.remove 2012-05-17 05:44:56 +02:00