Thanks, Alex - I'll take a look at socks for this. However, the latest versions of Apache also have regexp-based proxying. On the other hand - I haven't quite gotten it to work, either.
David On Thu, Nov 13, 2008 at 7:32 PM, Alex Loddengaard <[EMAIL PROTECTED]> wrote: > You could also have your developers setup a SOCKS proxy with the -D option > to ssh. Then have them install FoxyProxy. > The solution you're trying to do will make maintaining access to your > datanodes difficult. That is, for each new datanode, you'll have to add a > proxy rule to Apache. With the SOCKS setup, FoxyProxy can be configured to > use regular expressions, hence proxying all requests to any one of your > nodes. > > Googling for "SOCKS proxy ssh" should give you more info on how to get this > up and running. We used this set up for a hack contest we hosted at > ApacheCon and it worked well. > > Alex > > On Thu, Nov 13, 2008 at 12:19 PM, David Ritch <[EMAIL PROTECTED]> > wrote: > > > Has anyone configured Apache as a reverse proxy to allow access to your > > cloud? I'm having trouble doing this. > > > > I have a cloud. My datanodes are not visible outside the cloud for > > security. I'd like to provide some degree of access for my developers, > > using a proxy. I have Apache-2.2, and can get part of the way there, but > > I'm having trouble with the proxy rules and ports. > > > > I'm running a name node on NN, and Apache on WS. I'd like to be able to > go > > to http://WS/NN, and have that map to http://NN:50070/, and show me the > > NameNode status. > > > > I tried the naive configuration of Apache: > > > > ProxyPass /NN http://NN:50070 > > ProxyPassReverse /NN http://NN:50070 > > > > This maps the first page properly, and gets the redirect to dfshealth. > > However, it does not do the reverse remap, and I get > > http://WS/dfhshealth.jsp. > > > > So, I tried the following: > > > > ProxyPass /NN http://NN > > ProxyPassReverse /NN http://NN > > > > and accessed http://WS/NN:50070/ in my browser. Again, the initial > touch > > resulted in a successful proxy operation. This time, the rewrite of the > > reference succeeded, and my browser tried to access > > http://WS/NN:50070/dfshealth.jsp; however, this did not result in a > proxy > > operation. Instead, my web browser tried to access a local file > > /var/www/html/NN:50070. Apparently, it thought that would be a > directory, > > and dfshealth.jsp would be a file in it. > > > > So - what am I doing wrong? Is there a reason that I should be using an > > entirely different approach? > > > > Thanks! > > > > David > > >
