So, there's an annoying intercepting proxy which won't let you read stuff that looks interesting. What are you going to do about it? If you're me, you invent a ghastly thing out of bits of string and sellotape, and then have enough temerity left over to suggest that other people might want to use it too.
You need a browser with enough clue to be able to use a proxy autoconfigure script. That's pretty much any e-sewer browser since Netscape Navigator, but don't expect w3m to be able to use it.
The hack here has three parts.
I'm assuming that the HTTP proxy is friendly, but is slow and/or reluctant to carry seriously high volumes of stuff, so that it's a last resort rather than something you can just configure your browser to use by default for everything.
I'm so glad you asked me that. Here's what happens when you try to fetch a naughty resource.