Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

How do I fix "406 Client browser does not accept the MIME type of the requested page" when trying to view barclaysstockbrokersitrader.com?

  • 1 antwoord
  • 9 hierdie probleem
  • 2 views
  • Laaste antwoord deur cor-el

junctiontwo
junctiontwo
more options

The homepage (https://www.barclaystradinghub.co.uk/home/international-equities.html) opens ok, but after logging in to my account (https://www.barclaysstockbrokersitrader.com/Login/) I receive this error message:

406 Client browser does not accept the MIME type of the requested page

I have searched in vain for a solution..........please help!

The homepage (https://www.barclaystradinghub.co.uk/home/international-equities.html) opens ok, but after logging in to my account (https://www.barclaysstockbrokersitrader.com/Login/) I receive this error message: 406 Client browser does not accept the MIME type of the requested page I have searched in vain for a solution..........please help!

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Clear the cache and cookies only from websites that cause problems.

"Clear the Cache":

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

"Remove Cookies" from sites causing problems:

  • Firefox/Tools > Options > Privacy > Cookies: "Show Cookies"

Try to delete a possible user.js file and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js