Hi,
I am running nodejs behind a firewall and I am trying to issue an
outbound request when a client hits a certain URL on the running
nodejs (say, to http://search.twitter.com). The problem is that I'm in
a corporate environment and there's a proxy server that facilitates
internet access. As a result, HttpClient.request times-out.
I am wondering if it is possible to configure node for proxy access.
Start-up parameters would be great (curl/wget style)...
On Jun 22, 2010 3:21 PM, "florin" <dur...@gmail.com> wrote:
Hi, I am running nodejs behind a firewall and I am trying to issue an outbound request when a client hits a certain URL on the running nodejs (say, to http://search.twitter.com). The problem is that I'm in a corporate environment and there's a proxy server that facilitates internet access. As a result, HttpClient.request times-out. I am wondering if it is possible to configure node for proxy access. Start-up parameters would be great (curl/wget style)...
Any ideas? florin
-- You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com. To unsubscribe from this group, send email to nodejs+unsubscribe@googlegroups.com <nodejs%2Bunsubscribe@googlegroups.com>. For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.
> On Jun 22, 2010 3:21 PM, "florin" <dur...@gmail.com> wrote:
> Hi,
> I am running nodejs behind a firewall and I am trying to issue an
> outbound request when a client hits a certain URL on the running
> nodejs (say, tohttp://search.twitter.com). The problem is that I'm in
> a corporate environment and there's a proxy server that facilitates
> internet access. As a result, HttpClient.request times-out.
> I am wondering if it is possible to configure node for proxy access.
> Start-up parameters would be great (curl/wget style)...
> Any ideas?
> florin
> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+unsubscribe@googlegroups.com <nodejs%2Bunsubscribe@googlegroups.com>.
> For more options, visit this group athttp://groups.google.com/group/nodejs?hl=en.
On Wed, Jun 23, 2010 at 09:45, <r...@tinyclouds.org> wrote: > If I understand forward HTTP proxies correctly - it requires the > CONNECT method open a tunnel?
Yes, but not all HTTP proxies support it (or have it locked down, you can use it to e.g. tunnel SSH traffic). The simplest proxy call is something like:
On Wed, Jun 23, 2010 at 12:51 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > On Wed, Jun 23, 2010 at 09:45, <r...@tinyclouds.org> wrote: >> If I understand forward HTTP proxies correctly - it requires the >> CONNECT method open a tunnel?
> Yes, but not all HTTP proxies support it (or have it locked down, you > can use it to e.g. tunnel SSH traffic). The simplest proxy call is > something like:
> On Wed, Jun 23, 2010 at 12:51 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> > On Wed, Jun 23, 2010 at 09:45, <r...@tinyclouds.org> wrote:
> >> If I understand forward HTTP proxies correctly - it requires the
> >> CONNECT method open a tunnel?
> > Yes, but not all HTTP proxies support it (or have it locked down, you
> > can use it to e.g. tunnel SSH traffic). The simplest proxy call is
> > something like:
On Thu, Jun 24, 2010 at 10:03, florin <dur...@gmail.com> wrote: > Well, that's unfortunate since it makes it hard (impossible?) to test > nodejs when you're behind corp proxies...
> On Thu, Jun 24, 2010 at 10:03, florin <dur...@gmail.com> wrote:
> > Well, that's unfortunate since it makes it hard (impossible?) to test
> > nodejs when you're behind corp proxies...
On Thu, Jun 24, 2010 at 10:22, florin <dur...@gmail.com> wrote: > connect-proxy is only for SOCKS proxies. I gave it a shot with our > corp proxy, no go.
My copy from the Ubuntu repositories supports HTTP just fine. I'd suggest you update yours but I think connect-proxy hasn't been updated since 2006.
> On Thu, Jun 24, 2010 at 10:22, florin <dur...@gmail.com> wrote:
> > connect-proxy is only for SOCKS proxies. I gave it a shot with our
> > corp proxy, no go.
> My copy from the Ubuntu repositories supports HTTP just fine. I'd
> suggest you update yours but I think connect-proxy hasn't been updated
> since 2006.
