We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 1 antwurd
  • 9 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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!

Alle antwurden (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