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.
