I was using that approach as well before the latest source code that I pulled down. The trouble seemed to happen after that April 4th patch (http://issues.apache.org/jira/browse/SHINDIG-765). Now, the proxy settings on the jetty command line don't seem to do anything. I have been able to get it going again, but it is extremely ugly. I had to hardcode my proxy into the BasicHttpFetcher, so that I can get through another task. Then I will circle back and see if I can come up with a solution. I am working from the source code trunk and have been using Jetty. I haven't worked with Tomcat just yet.
Steve -----Original Message----- From: Fisher, Tim [mailto:[email protected]] Sent: Wednesday, April 15, 2009 5:14 PM To: [email protected] Subject: RE: Running Shindig behind a firewall Steve, Thanks for the input, I am looking forward to hear what you find out. Since my last post, I have been able to successfully run Shindig from behind my firewall and serve remote gadgets if I am using Jetty as the server. However, I still can not get it to recognize the proxy when running through Tomcat. To use a proxy with the Jetty server, you just need to start Shindig with this command: mvn -Prun -Dhttp.proxyHost=proxydomain -Dhttp.proxyPort=proxyport Tim -----Original Message----- From: Terlecki, Stephen [mailto:[email protected]] Sent: Wednesday, April 15, 2009 4:32 PM To: [email protected] Subject: RE: Running Shindig behind a firewall I am working on the same issue right now. I don't have 100% of the details just yet - I am still working on it, but I think with a recent fix (http://issues.apache.org/jira/browse/SHINDIG-765), proxy support was inadvertently disabled. Prior to that fix, BasicHttpFetcher was using HttpUrlConnection that dropped down to the java configured proxy settings to see if they needed to be set. BasicHttpFetcher was updated to use commons HttpClient that does not do that same thing. The proxy info needs to be configured manually. It looks like BasicHttpFetcher allows for a proxy provider to be used, but the guice @Inject annotation was commented out due to a previous fix (http://issues.apache.org/jira/browse/SHINDIG-718). I think there is just a disconnect here. I will post here when I have a definite on it. Steve T. -----Original Message----- From: Fisher, Tim [mailto:[email protected]] Sent: Wednesday, April 15, 2009 2:57 PM To: [email protected] Subject: Running Shindig behind a firewall Has anyone been successful in configuring Shindig to run behind a firewall? I currently have Shindig running with Tomcat on my local computer which is sitting behind our corporate firewall. I am able to access gadgets that are locally hosted just fine, however if I try to access a remote gadget, I run into connection problems. Shindig is not able to get through the Proxy. Doing a Google search, I've seen several suggestions of where to set proxy values to get this working, so far to no avail. Can anyone help me figure out what I need to do to get Shindig running behind a firewall? Thanks, Timothy Fisher The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
