Webpages full of "???????"

[Headend]

Since upgrading to 5.0.1.40y I seem to get some webpages loading full of question-marks and other extended ascii characters. Anyone else seeing this? I'm going to downgrade back to 4.2.1.8.

Headend
Tower: Mintek (82 was 12) - Signal: 19% - Firmware: 5.0.1.40y - 128k - Smoothwall and PPPoE

 

[Headend]

Damn - downgrade didn't help. Could it be their transparent proxy stuffing things up?

Headend
Tower: Mintek (82 was 12) - Signal: 19% - Firmware: 5.0.1.40y - 128k - Smoothwall and PPPoE

 

[regardtv]

Sounds more like you "codepage settings" ...

Internet Explorer: .. right click on the page, select Encoding and make sure that it's set to : Western European (Windows)

FireFox: Select Tools-->Options , Select Languages and check that encoding is set to Western

Hope this helps

 

[DFantom]

I've gotten that when either the font that is used I don't have or the web page is in a foreign language.

It may be the proxy, but that is an extreme long shot because it would require there proxy do content manipulation over and above what a normal proxy does.

--
D>Fantom
--------------------
:- Sentech -:
:- Radiokop Tower -:
:- 512K Package -:
--------------------

 

[Headend]

Thanks for the suggestions guys. Cleared my Mozilla cache and problem disappeared. Looks like I got some errors when I first loaded the page and was then loading the cached version no matter how often I refreshed.

Headend
Tower: Mintek (82 was 12) - Signal: 19% - Firmware: 5.0.1.40y - 128k - Smoothwall and PPPoE

 

[Ditch]

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by DFantom</i>
It may be the proxy, but that is an extreme long shot because it would require there proxy do content manipulation over and above what a normal proxy does.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
Not necessarily content manipulation, in theory it would only need to send an incorrect "Content-Encoding" HTTP header to mess up a page ..
in any case though, that wasn't the problem here.