You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@wookie.apache.org by Adrien Futschik <ad...@gmail.com> on 2010/03/23 10:52:09 UTC

issues with proxy & google gadgets

Hy everyone !

I am still facing proxy issues. I did not managed to pass proxy successfully
until today.
What's even more disturbing is that when trying to reach an internal RSS
feed (inside home network) I don't have any information.

I have tried to enable debug log-level in
wookie/WEB-INF/classes/log4j.properties, like this :
org.apache.wookie.proxy.ProxyClient=debug, widgety

but nothing shows'up in the log file.

I have added the <access origin="*"/> attribute in the config.xml file and
tried to use url = widget.proxify(url); method.

Here is how I have configured my proxy under widgetserver.properties :

#######################################################################
widget.proxy.usewhitelist=true
widget.proxy.checkdomain=false
##  local proxy settings - note if no hostname is specified then no proxy
will be used ##
widget.proxy.scheme=
widget.proxy.hostname=*HOSTNAME*
widget.proxy.port=*PORT*
## default is to use the Wookie whitelist proxy
widget.proxy.path=/wookie/proxy
## comment out the line above, and uncomment this to use the Shindig open
proxy instead
# widget.proxy.path=/gadgets/proxy
widget.proxy.username=*USER*
widget.proxy.password=*PASSWORD*
widget.proxy.usentlmauthentication=*true*

I have set "usentlmauthentication" property to true because I know that the
proxie uses ntlm authentication, but I am not sure
of how this is supposed to work under a linux server.

Would you have a simple widget sample that access Internet resource through
a proxy ? I trying to solve this for a little while now.

The other thing is about using Google Gadgets under wookie. I have'nt been
successfull with this.
I have tried importing this hello-the-world gadget :
http://people.portaildulibre.fr/~afutschik/bonjour.xml without success.

In the admin console, I have this message : "There was a problem registering
this gadget "
In the log file : Method failed: HTTP/1.1 404 Introuvable
http://160.1.159.20:8080/wookie/gadgets/metadataIntrouvable<html><head><title>Apache
Tomcat/6.0.24 - Rapport
d'erreur</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>Etat HTTP 404 - /wookie/gadgets/metadata</h1><HR size="1"
noshade="noshade"><p><b>type</b> Rapport d'état</p><p><b>message</b>
<u>/wookie/gadgets/metadata</u></p><p><b>description</b> <u>La ressource
demandée (/wookie/gadgets/metadata) n'est pas disponible.</u></p><HR
size="1" noshade="noshade"><h3>Apache Tomcat/6.0.24</h3></body></html>

Thanks in advance for your help,

Adrien

Re: issues with proxy & google gadgets

Posted by Adrien Futschik <ad...@gmail.com>.
On Tue, Mar 23, 2010 at 2:47 PM, Scott Wilson <
scott.bradley.wilson@gmail.com> wrote:

> On 23 Mar 2010, at 13:29, Adrien Futschik wrote:
>
> Well, once again, thank you Scott !!
>
>>
>> Is this running on Debian? Console output was redirected
>> to /var/log/syslog by default, and didn't show up in catalina.out.
>>
>> No it a CentOS but I am not using the default Tomcat package but a tar.gz
> file from Tomcat (apache-tomcat-6.0.24).  Nothing in /var/log/syslog or
> /var/log/messages
>
>
> OK, I think in order to be able to debug effectively you need to figure out
> where Tomcat is putting the logs! Normally there is some output in
> {tomcat}/logs/catalina.out ?
>

Here is a sample of the output of the catalina.out :
[...]
DEBUG [Thread-9] (WgtWatcher.java:80) - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
20:53:50,772 DEBUG WgtWatcher:80 - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
DEBUG [Thread-9] (WgtWatcher.java:80) - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
20:53:55,877 DEBUG WgtWatcher:80 - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
DEBUG [Thread-9] (WgtWatcher.java:80) - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
20:54:01,058 DEBUG WgtWatcher:80 - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
DEBUG [Thread-9] (WgtWatcher.java:80) - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
20:54:06,231 DEBUG WgtWatcher:80 - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
DEBUG [Thread-9] (WgtWatcher.java:80) - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
20:54:11,394 DEBUG WgtWatcher:80 - check for new widgets at
/opt/apache-tomcat-6.0.24/webapps/wookie/deploy
[...]

Re: issues with proxy & google gadgets

Posted by Scott Wilson <sc...@gmail.com>.
On 23 Mar 2010, at 13:29, Adrien Futschik wrote:

> Well, once again, thank you Scott !!
> 
> Is this running on Debian? Console output was redirected to /var/log/syslog by default, and didn't show up in catalina.out.
> 
> No it a CentOS but I am not using the default Tomcat package but a tar.gz file from Tomcat (apache-tomcat-6.0.24).  Nothing in /var/log/syslog or /var/log/messages

OK, I think in order to be able to debug effectively you need to figure out where Tomcat is putting the logs! Normally there is some output in {tomcat}/logs/catalina.out ?

S

Re: issues with proxy & google gadgets

Posted by Adrien Futschik <ad...@gmail.com>.
Well, once again, thank you Scott !!



> Is this running on Debian? Console output was redirected
> to /var/log/syslog by default, and didn't show up in catalina.out.
>
> No it a CentOS but I am not using the default Tomcat package but a tar.gz
file from Tomcat (apache-tomcat-6.0.24).  Nothing in /var/log/syslog or
/var/log/messages

The "weather" widget does this, so would be worth trying.
>
Well, he "weather" widget doen't work for me. There'is nothing in the log
(catalina.out)


>
> Note that the widget access policy is currently only loaded when the widget
> is dropped into the "deploy" folder, and not when added through the "admin"
> web interface.
>
> If I am right, the weather widget was dropped into the deploy folder


> Look for  a line in the log (or catalina.out, or syslog...) that says
> something like:
>
> 11:12:14,753  INFO WidgetFactory:213 - access policy granted for tweetWatch
> to access http://twitter.com
> 11:12:14,754  INFO ContextListener:178 - tweetWatch' - Widget was
> successfully imported into the system.
>
> The other thing is about using Google Gadgets under wookie. I have'nt been
> successfull with this.
> I have tried importing this hello-the-world gadget :
> http://people.portaildulibre.fr/~afutschik/bonjour.xml<http://people.portaildulibre.fr/%7Eafutschik/bonjour.xml>without success.
>
>
> It would appear that your Shindig server is not available at the location
> set in your configuration?
>
Well, actually, I did not install any Shinding server. I am not sure what
this is.

>
>
I managed it OK with my setup, so there is nothing wrong with your gadget:
>

I can see that :) Thanks for testing !

>
>
> For simplicity, I usually install Shindig as the Tomcat root webapp and
> then have wookie configured as follows:
>
> # Location of Shindig services
> widget.shindig.url=/
> widget.metadata.url=/gadgets/metadata
>
> (Note that Shindig isn't installed by default with Wookie, you need to go
> to the Shindig project and get the .war file.)
>

I'll try and install it and come back to you.

Adrien

Re: issues with proxy & google gadgets

Posted by Scott Wilson <sc...@gmail.com>.
On 23 Mar 2010, at 09:52, Adrien Futschik wrote:

> Hy everyone !

Hi Adrien!

> I am still facing proxy issues. I did not managed to pass proxy successfully until today.
> What's even more disturbing is that when trying to reach an internal RSS feed (inside home network) I don't have any information.
> 
> I have tried to enable debug log-level in wookie/WEB-INF/classes/log4j.properties, like this :
> org.apache.wookie.proxy.ProxyClient=debug, widgety
> 
> but nothing shows'up in the log file.

Is this running on Debian? Console output was redirected to /var/log/syslog by default, and didn't show up in catalina.out.

> I have added the <access origin="*"/> attribute in the config.xml file and tried to use url = widget.proxify(url); method.
> 
> Here is how I have configured my proxy under widgetserver.properties :
> 
> #######################################################################
> widget.proxy.usewhitelist=true
> widget.proxy.checkdomain=false
> ##  local proxy settings - note if no hostname is specified then no proxy will be used ##
> widget.proxy.scheme=
> widget.proxy.hostname=HOSTNAME
> widget.proxy.port=PORT
> ## default is to use the Wookie whitelist proxy
> widget.proxy.path=/wookie/proxy
> ## comment out the line above, and uncomment this to use the Shindig open proxy instead
> # widget.proxy.path=/gadgets/proxy
> widget.proxy.username=USER
> widget.proxy.password=PASSWORD
> widget.proxy.usentlmauthentication=true
> 
> I have set "usentlmauthentication" property to true because I know that the proxie uses ntlm authentication, but I am not sure
> of how this is supposed to work under a linux server.
> 
> Would you have a simple widget sample that access Internet resource through a proxy ? I trying to solve this for a little while now.

The "weather" widget does this, so would be worth trying.

Note that the widget access policy is currently only loaded when the widget is dropped into the "deploy" folder, and not when added through the "admin" web interface.

Look for  a line in the log (or catalina.out, or syslog...) that says something like:

11:12:14,753  INFO WidgetFactory:213 - access policy granted for tweetWatch to access http://twitter.com
11:12:14,754  INFO ContextListener:178 - tweetWatch' - Widget was successfully imported into the system.

> The other thing is about using Google Gadgets under wookie. I have'nt been successfull with this.
> I have tried importing this hello-the-world gadget :  http://people.portaildulibre.fr/~afutschik/bonjour.xml without success.

It would appear that your Shindig server is not available at the location set in your configuration?

I managed it OK with my setup, so there is nothing wrong with your gadget:



For simplicity, I usually install Shindig as the Tomcat root webapp and then have wookie configured as follows:

# Location of Shindig services
widget.shindig.url=/
widget.metadata.url=/gadgets/metadata

(Note that Shindig isn't installed by default with Wookie, you need to go to the Shindig project and get the .war file.)

> In the admin console, I have this message : "There was a problem registering this gadget "
> In the log file : Method failed: HTTP/1.1 404 Introuvable http://160.1.159.20:8080/wookie/gadgets/metadata Introuvable<html><head><title>Apache Tomcat/6.0.24 - Rapport d'erreur</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>Etat HTTP 404 - /wookie/gadgets/metadata</h1><HR size="1" noshade="noshade"><p><b>type</b> Rapport d'état</p><p><b>message</b> <u>/wookie/gadgets/metadata</u></p><p><b>description</b> <u>La ressource demandée (/wookie/gadgets/metadata) n'est pas disponible.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.24</h3></body></html>
> 
> Thanks in advance for your help,
> 
> Adrien