On 29 October 2011 01:43, Ross Gardler <[email protected]> wrote: > On 29 October 2011 01:28, Ross Gardler <[email protected]> wrote: >> Any idea why I'm being asked to login to wookie (via basic >> authentication) to access a proxied URL. >> >> e.g. >> http://localhost:8080/wookie/proxy?instanceid_key=Mwp1GaQDZoyOOVvjnQ.sl.withW4DE.eq.&url=http://api.twitter.com/1/statuses/show.xml?id=129284508087357440&include_entities=false >> >> Accessing the URL directly in the browser presents no problem. > > It seems there is an OAuth challenge on the proxied request, but not > on the browser request. Strange... > > I'm still stumped.
I've now tested this with another widget that is accessing a different REST API. Same result. Again, there is no need for authentication on this API and entering the URL directly in the browser works just fine. I'm still trying to debug, but if anyone has any pointers as to why this might be happening (remember, it has only just started happening - everything worked fine just a couple of days ago). Ross > >> >> The weather widget (which also makes a proxied request) works fine. >> >> The strange thing is that I was not seeing this behaviour earlier >> today. I've done a clean build and removed the database. >> >> Any ideas? >> >> Ross >> >> -- >> Ross Gardler (@rgardler) >> Programme Leader (Open Development) >> OpenDirective http://opendirective.com >> > > > > -- > Ross Gardler (@rgardler) > Programme Leader (Open Development) > OpenDirective http://opendirective.com > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
