Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Cannot get freestockcharts.com to display correctly

  • 3 réponses
  • 1 a ce problème
  • 1 vue
  • Dernière réponse par dennyjewell

more options

see attachment and thanks in advance for your help.

see attachment and thanks in advance for your help.
Captures d’écran jointes

Toutes les réponses (3)

more options

The encoding seems to be wrong, i.e., the way the characters are encoded does not match the font you're using on the page. I'm not sure from the URL, but is that just the home page here:

http://www.freestockcharts.com/

If you right-click the page and choose View Page Info, what do you see for the middle items Type and Text Encoding (see attached screenshot).

more options

You can try these steps in case of issues with web pages:

You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • Hold down the Shift key and left-click the Reload button
  • Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • Press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies from websites that cause problems.

"Clear the Cache":

  • Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"

"Remove the Cookies" from websites that cause problems:

  • Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

Start Firefox in Safe Mode to check if one of the extensions (3-bar Menu button/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: 3-bar Menu button/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window

What security software do you have?

Make sure that your security software isn't modifying the HTTP response headers.

more options

Thanks for the suggestions - release 44 fixed the problem.