Shindig 1.0 used a Guice injected proxy provider -- more info on using 1.0 with 
a proxy can be found here:

http://markmail.org/message/omlzchaspedwbagv

--Jesse

-----Original Message-----
From: Jeremy Mason [mailto:[email protected]] 
Sent: Monday, September 21, 2009 12:01 PM
To: [email protected]
Subject: Re: Running Shindig behind a firewall

Thanks. Downloading the latest and running using Jetty from the base
directory with command line mvn -Dmaven.test.skip -Dhttp.proxyHost=<>
-Dhttp.proxyPort=8080 -Prun works. After a "mvn clean install". It also
works on Tomcat running from root.

The problem was caused by me downloading the war from
http://incubator.apache.org/shindig/download/index.html, specifically
https://repository.apache.org/content/groups/public/org/apache/shindig/shindig-server/1.0-incubating/shindig-server-1.0-incubating.war.
This war or the way I installed it does seem to have an issue with proxies.

Jeremy

On Mon, Sep 21, 2009 at 4:00 PM, Terlecki, Stephen <
[email protected]> wrote:

> I run behind a firewall and don't have trouble with the firewall settings.
>  When running jetty in dev, I pass the proxy settings through the command
> line with -D params.  For configuration out on the servers, we use the
> catalina properties and everything works well.
>
> Maybe there is something else blocking.
>
> I am working with latest from the trunk.
>
> Steve T.
>
> -----Original Message-----
> From: Jeremy Mason [mailto:[email protected]]
> Sent: Monday, September 21, 2009 9:49 AM
> To: [email protected]
> Subject: Re: Running Shindig behind a firewall
>
> Hi, picking up again after being out of this for some months. Using Tomcat
> I'm getting the company firewall issue. Setting entries in
> catalina.properties or -D java command line seems not to work. Monitoring
> the network traffic shows the proxy settings are being ignored. I'm going to
> pull latest code from head, rebuild and see if there is a patch. Also run
> using Jetty. Would appreciate any comments.
> Jeremy
>

Reply via email to