00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:10:03  * devdazedquit (Quit: Computer has gone to sleep.)
00:13:22  * Fishrock123quit (Quit: Leaving...)
00:36:07  * c4miloquit (Remote host closed the connection)
00:37:18  * c4milojoined
00:39:22  * mattmcclurejoined
00:41:37  * c4miloquit (Ping timeout: 240 seconds)
00:45:02  * watildequit (Remote host closed the connection)
01:28:36  * abraxas_joined
01:33:09  * abraxas_quit (Ping timeout: 245 seconds)
02:04:27  * jeffmjackquit (Quit: Connection closed for inactivity)
02:10:12  * abraxas_joined
03:03:24  * mattmcclurequit (Quit: Connection closed for inactivity)
03:28:23  * user__joined
03:28:28  <user__>hi!
03:29:17  <user__>can i get some help
03:29:19  <user__>pls
03:30:58  * user__quit (Client Quit)
05:45:41  * mrjazzcatquit (Quit: Leaving)
06:59:47  * abraxas_quit (Remote host closed the connection)
07:20:03  * lpinjoined
08:27:59  * Pagebakersjoined
08:40:43  * Pagebakersquit (Remote host closed the connection)
08:43:11  * Pagebakersjoined
08:47:38  * Pagebakersquit (Ping timeout: 256 seconds)
09:02:06  * Nodejitsu-Githubjoined
09:02:06  <Nodejitsu-Github>[node-http-proxy] indexzero pushed 2 new commits to master: http://git.io/3FuAqA
09:02:06  <Nodejitsu-Github>node-http-proxy/master 4947484 Brett Kochendorfer: Update README.md for benchmarks...
09:02:06  <Nodejitsu-Github>node-http-proxy/master c82c9ec Charlie Robbins: Merge pull request #625 from bkochendorfer/master...
09:02:06  * Nodejitsu-Githubpart
09:03:11  * travis-cijoined
09:03:11  <travis-ci>nodejitsu/node-http-proxy#626 (master - c82c9ec : Charlie Robbins): The build passed.
09:03:11  <travis-ci>Change view : https://github.com/nodejitsu/node-http-proxy/compare/3311106c2c23...c82c9ece8a0b
09:03:11  <travis-ci>Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/44553300
09:03:11  * travis-cipart
09:05:39  * chjjquit (Read error: Connection reset by peer)
09:06:05  * chjjjoined
09:06:06  * azooljoined
09:49:29  * Sebastien-Ljoined
11:14:21  * joshonthewebquit (Ping timeout: 250 seconds)
11:15:36  * azoolquit (Remote host closed the connection)
11:17:18  * joshonthewebjoined
12:40:41  * lpinquit (Quit: Textual IRC Client: www.textualapp.com)
12:59:13  * Sebastien-Lquit (Ping timeout: 265 seconds)
13:57:59  * mrjazzcatjoined
14:01:19  * Sebastien-Ljoined
14:32:30  * lpinjoined
14:32:46  * Fishrock123joined
15:01:10  * devdazedjoined
15:11:10  * Sebastien-Lquit (Ping timeout: 265 seconds)
16:44:10  * c4milojoined
16:45:10  * c4miloquit (Read error: Connection reset by peer)
16:45:14  * c4milo_joined
17:18:26  * _yoy_quit (Ping timeout: 250 seconds)
17:38:36  * Sebastien-Ljoined
18:01:32  * patrickclancyjoined
18:17:18  * chjjquit (Read error: Connection reset by peer)
18:18:16  * chjjjoined
19:06:04  * ELLIOTTCABLE_joined
19:06:07  * jeffmjackjoined
19:07:50  * marcoceppi_joined
19:08:17  * sebastien__joined
19:08:20  * funnel_joined
19:08:38  * owenb____quit (Ping timeout: 244 seconds)
19:08:39  * funnelquit (Ping timeout: 244 seconds)
19:08:39  * ELLIOTTCABLEquit (Ping timeout: 244 seconds)
19:08:39  * Sebastien-Lquit (Ping timeout: 244 seconds)
19:08:40  * marcoceppiquit (Ping timeout: 244 seconds)
19:09:29  * funnel_changed nick to funnel
19:10:10  * owenb____joined
19:13:05  * ELLIOTTCABLE_changed nick to ELLIOTTCABLE
19:40:47  * lpinquit (Quit: Textual IRC Client: www.textualapp.com)
19:43:10  * sebastien__quit (Ping timeout: 258 seconds)
19:51:00  * rcombsquit (Read error: Connection reset by peer)
19:51:32  * rcombsjoined
20:08:00  * lpinjoined
20:21:52  * chjjquit (Read error: Connection reset by peer)
20:22:22  * chjjjoined
20:39:03  * chjjquit (Read error: Connection reset by peer)
20:39:40  * chjjjoined
21:15:59  * cronopiojoined
21:34:38  * patrickclancyquit (Quit: patrickclancy)
22:06:57  * Fishrock123quit (Remote host closed the connection)
22:22:54  * c4milo_quit (Remote host closed the connection)
22:27:42  * lpinquit (Quit: Leaving)
22:31:57  * lbodjoined
22:32:19  * Fishrock123joined
22:34:57  <lbod>hi and sorry this is a generic question but im using a library that doesnt use node-http-proxy.. & it doesnt work behind a proxy :) im right thinking that carving http headers appropriately through a proxy isnt easy? ive read lots of docs on this now, i believe the library im using just doesnt support it, where can i get the best information on this? (apart from reading the rfc!!)
22:39:26  * c4milojoined
22:40:13  * c4milo_joined
22:40:15  * c4miloquit (Read error: Connection reset by peer)
22:43:54  <cronopio>lbod: hi still there?
22:44:12  <lbod>hi yeh, still here
22:44:16  <cronopio>lbod: what are you trying to do?
22:44:39  <lbod>requests from a node process via a proxy to the internet
22:44:57  <cronopio>ok and the proxy is a full HTTP proxy, right?
22:45:06  <lbod>it's a longer story, it's going through various libraries
22:45:36  <cronopio>so is possible that at any point the request is nuked or something
22:45:52  <lbod>the proxy is fine, i can send requests through it with other libraries.. im trying to narrow down what headers are wrong.. ive been doing alot of wireshark sniffing
22:46:09  <lbod>the library im using (i think) is wrong
22:46:31  <cronopio>ok so the proxy is requiring you to set some specific headers or will drop the request?
22:47:05  <cronopio>lbod: even if you did a mistake on writting headers the request should go out and get a failure response from the destinatary
22:47:12  <lbod>no, it's almost a pass through proxy for us... hmm, im not explaining weel
22:47:58  <lbod>but there are dependencies like the (i could be wrong, had a few beers now).. the path header must be set to the full url
22:48:17  <lbod>the host and port headers are set to the proxies
22:48:23  <cronopio>lbod: if you are doing http requests the node library to that should mikeal's request module
22:48:42  <cronopio>lbod: oh
22:48:51  <lbod>yeh, this is my issue.. im using a library called dojo, its client side, it also does node side
22:49:05  <lbod>i think it's node request module is wrong
22:49:49  <lbod>i *think* it's not drafting http headers correctly but i could be wrong again
22:49:56  <lbod>*crafting
22:51:23  <cronopio>lbod: ok, so I think to debug that you should see where in the code is doing the native call http.request(), the object returned from that you console.log its headers and you'll see the exact headers that are sending on the request
22:51:29  <lbod>http://dojotoolkit.org/reference-guide/1.10/dojo/request/node.html - it's not important but this is a front end lib that also works server side
22:52:14  <cronopio>lbod: I see you'll need to dig into the code and set some console.log to get more info about the request structure
22:52:28  <lbod>yeh ive done that. i went down to wireshark
22:53:11  <lbod>i hacked it to the point the only header i couldnt get rid of was a authorization header...
22:53:43  <lbod>and thats as far as ive got before pulling my hair out and jumping off a bridge...
22:54:42  <lbod>conopio: have you worked on node-http-proxy?
22:54:53  <cronopio>lbod: yes a bit
22:55:24  <lbod>am i right thinking the path header has to be the full url?
22:55:25  <cronopio>well proxying http on node is as trivial as req.pipe(res)
22:55:35  <cronopio>lbod: yes sure
22:55:43  <cronopio>without domain and port
22:55:47  <lbod>host = proxy address/ip
22:55:52  <cronopio>just the path starting with /
22:55:59  <lbod>port = proxy port
22:57:05  <cronopio>and full I mean for all parameters on url
22:57:55  <cronopio>lbod: path header should be as that and the Host header should be the domain and port
22:58:19  <lbod>can you show me?
23:00:13  <lbod>maybe just misunderstanding but: path : http://www.someurl.com.page1 port : <proxy port> host : <proxy host>
23:00:34  <cronopio>lbod: oh well. a nodejs specofic implementation could be ussing http.request() method. That method accept hostname, port, path and method parameters. Are you refering to that?
23:00:49  <cronopio>lbod: because any other lib could accept parameters different
23:00:50  <lbod>yes
23:01:11  <cronopio>lbod: here is the example http://nodejs.org/api/http.html#http_http_request_options_callback
23:02:23  <lbod>:D here is the route of mines https://github.com/dojo/dojo/blob/master/request/node.js
23:03:11  <lbod>am not expecting you to read that
23:04:12  * devdazedquit (Quit: Computer has gone to sleep.)
23:04:49  <cronopio>lbod: ok so far https://github.com/dojo/dojo/blob/master/request/node.js#L90-L101 I think that is not a proper way to proxy the response back to the client
23:05:42  <cronopio>lbod: have to go out now, if need general nodejs advice contact me on [email protected] if need heelp with node-http-proxy over github is ok and if need support with any Nodejitsu service feel free to reach us over [email protected]
23:06:11  <lbod>thank you very much, thats wonderful support.. take care
23:06:37  <cronopio>lbod: thanks :D, take care you too
23:06:42  * cronopioquit (Quit: leaving)