PDA

View Full Version : Proxy settings not always respected



dloomer
June 3rd, 2009, 10:37 PM
I've set up a proxy (actually just pointing to a local version of Charles Proxy) both in my Safari network preferences and in Boxee itself. Charles Proxy runs at 127.0.0.1 (localhost), port 8888.

Evidence suggests that in some cases Boxee connects through the proxy, and in some cases it doesn't:

- Requests initiated within my app (both using urllib and the Player.Play() method) never show up in the Charles Proxy recording logs.
- If I shut down Charles Proxy while Boxee is running, which should disable all network connectivity in Boxee, my app still connects to the Internet while the rest of Boxee does not.

Is this a shortcoming in Boxee, or do I have to somehow explicitly indicate that my app should use Boxee's global proxy setting?

Bottom line is I'm trying to use Charles Proxy to debug my own app to see exactly what request headers it's sending to a third party, but it's not able to give me the results I need.

Thanks!

dloomer
June 4th, 2009, 10:11 PM
Just to make sure I wasn't missing a setting in my app, I tried it with the Netflix app, and same thing. Charles Proxy shows some requests to app.boxee.tv, and a few requests to the Netflix servers to grab images, but when I play a movie, nothing. If I shut off the proxy server (so that really, nothing network-dependent in Boxee should work if it was sending everything through my designated proxy as it should), I can still start up a movie but I can't browse my queues or recommendations. Seems pretty inconsistent.

So does nobody know anything about this? This proxy issue is extremely frustrating and a big blow to being able to debug some cookie-related problems in my app. Between this and the lack of good documentation and apparent lack of Team Boxee developers in this forum and lack of other developers reading this forum who have had to solve the same problems I'm trying to, I'm left pretty much dead in the water with my project.