Programatically you are pretty much stuck...it's probably a proxy filtering, which means:
Internet <=> Proxy <=> You
That when the site gets to the proxy, the proxy says no... and you (more than likely) have no other way to connect.
There are probably roundabout ways around this, but your best bet (and safest) is to explain your case and try to get things changed.
--------------
"But what of all those sweet words you spoke in private?"
"Oh that's just what we call pillow talk, baby, that's all."
| [reply]
[d/l] |
Beware of trouble - it may be bigger than you want. That said, it is possible to sidestep proxies by viewing the output of an unproxied browser. F'rinstance, I log into my home machine from work via SSH. I forward X traffic via SSH, so I can, from a terminal session on my home machine, open a web browser. I see what my home computer accesses, because that information is sent to me down my SSH tunnel. This is not speedy or particularly trivial.
The advice I'd give is that conversation is easier and safer than circumvention.
| [reply] |
