this works for me,
*://*.pandora.com/*
However this was a controlled test in the US where other programs were accessing Internet directly, meaning it is possible that Adobe was accessing the Internet directly. the websites I googled for people having problems with this & couldn't find any. a few other sites have posted pac files routing through tor & modified my pattern from that. (another site also did the same thing except with a PAC file.)
there are more patterns posted in the original guide I based this on. they may help speed up Pandora. the first pattern is whitelisted. I would use *://*.pandora.com/* or *.pandora.com/* instead, the pattern the tutorial posted could affect other sites with .pandora. in the url, forcing it in the proxy as well.
these patterns are blacklisted, again they are not needed but may speed up some things.
I did not test this to see if it causes pandora to quit again.
*audio*.pandora.com*
*pandora.com/images/*
*blog*.pandora.com*
this is also a blacklisted pattern, I have a feeling this will cause pandora to quit working out of the US, but I did not test the blacklisted patterns,
*.swf*
If you're still having
If you're still having problems with Pandora, please read this.
pandora.com through Tor exit nodes in US
I have determined that only 2 whitelist URL patterns are required to be passed through a Tor exit node in the US in order to listen to pandora:
Pandora Homepage: http://www.pandora.com/
Pandora Player: http://www.pandora.com/radio/xmlrpc/*
Nathan
Nice work, Nathan. Pretty
Nice work, Nathan. Pretty soon we'll be able to share these patterns directly through FoxyProxy.
Eric