1.0.3.101.gbfa97dfe Release: Still No Images Behind Proxy

[brandonmerritt]

I've searched for an update to this issue, but there doesn't seem to be a verified solution beyond downgrading the app.

The standing issue is that I'm unable to see any images behind my work proxy.

We have both an http and and https prox. Neither require a username or password login.

Prior to the 1.0.3 update I was able to see all album and user images.

my prefs look like this:

app.autostart-banner-seen=true
core.flash_version=16
autologin.username="someuser"
network.proxy.addr="http.proxy.somecompany.com:1234@https"
autologin.blob="a blob"
autologin.canonical_username="someuser"
language="en"
network.proxy.mode=2
core.clock_delta=0

I've tried installing and uninstalling Spotify.

Mostly I just want to verify that this is a known issue and it's being worked on.

[deannnnn]

I have this problem, too. In the Spotify 0.x versions, I was able to change "https" to "http" in the prefs file and it completely solved the problem. Trying to do this in Spotify 1.x, however, completely breaks Spotify's ability to connect to the network. Would love a solution.

[brandonmerritt]

Over 8 months since this thread was opened. There are NUMEROUS threads on this issue and none have a community advocating giving any indication that Spotify even acknowledges this is an issue.

It's nearly impossible to debug this problem since all the code in the App Package is obfuscated. Here's what I know:

• If I disconnect from the proxy and remove any reference to the proxy I get pictures
• Any pictures that are downloaded while "off proxy" are cached and they show up normally in the app once I'm back on the proxy
• Removing network.proxy.addr from the "prefs" file but leaving "network.proxy.mode=2" while off proxy will prevent me from downloading images
• Changing "network.proxy.mode=2" to 1 while off proxy allows me to download images
• I don't get any meaningful errors in my console, but from time to time "Spotify Helper" shows up

Honestly, none of should be surprising. I can't do any more troubleshooting on my end. Was hoping a Community Advocate (familiar with the issue) would weigh in.