Am I still the only one having troubles getting foo_discogs to work at all, I mean not getting any results at all.
The strange thing is that it works just fine when routing foobar requests through a proxy, either one in the local machine or one in a remote server. Any clue on this?
I tried to diagnose this but I run out of ideas, what could be stopping foo_discogs that is not active when setting up a proxy in foobar's network settings?
Just to be sure nothing in my network connection is interfering this is the captured network traffic for one discogs request:
GET /search?type=artists&q=Lila%20Downs HTTP/1.1
Host: api.discogs.com
Connection: close
Accept-Encoding: gzip
User-Agent: Opera/9.50
Accept: application/xml
Icy-MetaData:1
HTTP/1.1 200 OK
Content-Length: 292
Content-Encoding: gzip
Reproxy-Status: yes
Content-Type: application/xml; charset=utf-8
Date: Wed, 31 Aug 2011 15:16:36 GMT
Server: lighttpd
Connection: close
Same request sent through Firefox (minus the deleted auth cookies):
GET /search?type=artists&q=Lila%20Downs HTTP/1.1
Host: api.discogs.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
DNT: 1
Connection: keep-alive
Cookie: <snip>
Cache-Control: max-age=0
HTTP/1.1 200 OK
Content-Length: 292
Content-Encoding: gzip
Reproxy-Status: yes
Content-Type: application/xml; charset=utf-8
Date: Wed, 31 Aug 2011 15:18:56 GMT
Server: lighttpd
Connection: keep-alive
I think everything looks right, can someone compare and confirm?