yawnt
a74cd85c8a
socket.io stuff
2013-09-13 20:49:52 +02:00
yawnt
4a4607d075
support websockets
2013-09-13 20:06:51 +02:00
yawnt
0fb33810f5
merge with @cronopio
2013-09-13 19:08:34 +02:00
yawnt
c9cd6d2ad3
[fix] make @mmalecki a happy camper
2013-09-13 19:07:34 +02:00
cronopio
8b3fe32f6a
[tests] added the ws passes test and the streams webscokets test
2013-09-10 19:36:19 -05:00
cronopio
e0faaaf811
[fix] minor and short fixes
2013-09-10 19:31:47 -05:00
yawnt
1993faf8a4
new error propagation - follows
2013-09-05 17:45:03 +02:00
yawnt
3a39e444ff
new error propagation
2013-09-05 17:44:23 +02:00
yawnt
07551c63e4
websocket draft
2013-09-05 17:28:25 +02:00
cronopio
79f7f99528
[lib] initial draft to websockets passes
2013-09-03 14:09:35 -05:00
yawnt
4480699d3a
[fix] use some
2013-09-03 20:57:22 +02:00
yawnt
a6256cac1d
[fix] short circuit
2013-09-03 20:56:18 +02:00
cronopio
b85aa16e75
[test] test onError part, proxying to no where
2013-08-28 14:01:55 -05:00
cronopio
27df8d72ad
[test] testing the onResponse proxy method
2013-08-28 13:45:09 -05:00
yawnt
abf1d90fdf
[fix] use agent pool
2013-08-28 15:22:04 +02:00
yawnt
c9612798f1
[test] proxystream test
2013-08-28 14:58:57 +02:00
yawnt
8fc3389367
[test] add test for forwardstream
2013-08-28 14:49:27 +02:00
yawnt
f4e9945856
Merge pull request #3 from yawnt/tests
...
Tests
2013-08-28 05:18:08 -07:00
cronopio
2fac7b9b00
[test] added the lib/caronte/streams/forward.js initial test, one test pending
2013-08-26 16:34:32 -05:00
cronopio
c02b721321
[test] passes/web.js XHeaders func
2013-08-26 00:21:30 -05:00
yawnt
d40e4beb62
[test] passes/web.js (first 2 funcs)
2013-08-21 17:37:38 +02:00
yawnt
356f43d719
[fix] ProxyStraem now works
2013-08-20 17:32:29 +02:00
yawnt
d4f0da898e
[fix] some stuff start debugging proxystream
2013-08-20 16:09:37 +02:00
yawnt
9ab8749a9b
[feature] started working on error propagation, kinda sucks, gotta think it over
2013-08-10 20:41:25 +02:00
yawnt
bd3df45010
[fix] woops
2013-08-09 20:52:55 +02:00
yawnt
2e7343d728
[fix] making @jcrugzz a happy camper
2013-08-09 20:52:21 +02:00
yawnt
6a4294cbdf
[feature] implement _write and _read
2013-08-09 19:40:40 +02:00
yawnt
4f24664e8a
[api] add draft for proxystream
2013-08-09 19:37:58 +02:00
yawnt
cedc5c4bd2
[tests] add more tests
2013-08-09 19:13:44 +02:00
yawnt
335af81d02
[minor] remove coverage
2013-08-09 18:59:20 +02:00
yawnt
a255f984fe
[fix] tests
2013-08-09 18:58:56 +02:00
yawnt
16eacfa961
[test] started writing tests
2013-08-03 16:54:48 +02:00
yawnt
004a46c09d
[test] COVERAGE
2013-08-03 16:44:23 +02:00
yawnt
34f16e7464
[fix] making @stoke a happy camper
2013-08-03 15:56:05 +02:00
yawnt
d05af4af60
[refactor docs] add descriptions
2013-08-03 15:45:07 +02:00
yawnt
8273cb6461
[refactor] move to leaner architecture
2013-08-03 08:47:07 +02:00
yawnt
4d13156721
[dist] first
2013-08-01 10:50:39 +02:00
Maciej Małecki
ebbba73eda
[test] Test on newer version of node
2013-06-20 15:37:48 +02:00
Maciej Małecki
2fd748fb61
[dist] Bump version to 0.10.3
v0.10.3
2013-06-20 15:29:14 +02:00
Maciej Małecki
e1d384e769
[fix] Respect maxSockets from target options in RoutingProxy
2013-06-20 15:28:47 +02:00
Charlie Robbins
5ff2b6e1a1
Merge pull request #419 from Raynos/patch-1
...
Pass default certs to SNICallback example
2013-06-14 19:20:24 -07:00
Raynos
f5e1844abd
Pass default certs to SNICallback example
...
Using only SNICallback to create a HTTPS / TLS server is bad. It means all non SNI clients can't do anything because there are no certs.
in v0.10 of node TLS server was updated to throw if you forgot to supply certs.
Which means that every HTTPS server needs to supply certs as a fallback for when SNI is not available.
- closes #399
2013-05-10 17:55:01 -06:00
Emilien Kenler
0c753234c0
Send path in req.path and not the url
...
Signed-off-by: Emilien Kenler <hello@emilienkenler.com>
2013-05-04 22:48:50 +02:00
indexzero
de0928f616
[dist] Version bump. 0.10.2
v0.10.2
2013-04-21 17:06:54 -04:00
indexzero
7fc39d77f4
[minor] Strip trailing whitespace.
2013-04-21 17:02:18 -04:00
indexzero
59b71c033f
[minor] Style compliance. Fixes #402 .
2013-04-21 17:01:20 -04:00
Ivan Jaramillo
985025c90f
Add headers on 'handshake'
...
The headers in the 'handshake' event were not written to the socket, the client received data but not the headers.
2013-04-21 16:59:08 -04:00
Charlie Robbins
98f5c462ea
Merge pull request #407 from GUI/master
...
Correct keep-alive responses to HTTP 1.0 clients
2013-04-21 13:25:35 -07:00
Nick Muerdter
daf53bd753
Don't test raw HTTP 1.0 requests over HTTPS.
2013-04-18 18:11:58 -06:00
Nick Muerdter
a29b5e8e28
Correct keep-alive responses to HTTP 1.0 clients.
...
Since the proxy requests comes from NodeJS's HTTP 1.1 request client, a
backend server may default to setting Connection: keep-alive in its
response. However, the real HTTP 1.0 client may not be able to
handle that.
Force HTTP 1.0 client's to Connection: close, unless the client
explicitly supports keep-alive.
2013-04-18 16:33:10 -06:00