Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

FF 4.0.1 gets Bad Request - Invalid Verb [HTTP Error 400. The request verb is invalid.] on MSDN when ESET Node32 installed

  • 2 yanıt
  • 9 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: CodeSlinger

more options

FF 4.0.1 gets "Bad Request - Invalid Verb" [HTTP Error 400. The request verb is invalid.] on MSDN when ESET Node32 installed.

I have the latest version of ESET Nod32 installed [4.0.417.0] and always get this error with this and the previous beta version of FF4 unless I disable Nod32 "Web Access Protection". This does not happen with IE9. OS is Windows 7 x64 and is up to date. This has happened since I installed V4 of FF last November. I have tried everything I can think of but only disabling Nod32 web access protection allows MSDN to work. Other sites are fine.

This happens merely going to http://msdn.microsoft.com

FF 4.0.1 gets "Bad Request - Invalid Verb" [HTTP Error 400. The request verb is invalid.] on MSDN when ESET Node32 installed. I have the latest version of ESET Nod32 installed [4.0.417.0] and always get this error with this and the previous beta version of FF4 unless I disable Nod32 "Web Access Protection". This does not happen with IE9. OS is Windows 7 x64 and is up to date. This has happened since I installed V4 of FF last November. I have tried everything I can think of but only disabling Nod32 web access protection allows MSDN to work. Other sites are fine. This happens merely going to http://msdn.microsoft.com

CodeSlinger tarafından tarihinde düzenlendi

Tüm Yanıtlar (2)

more options

This issue can be caused by corrupted cookies.

Clear the cache and the cookies from sites that cause problems.

  • "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
  • "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
more options

@Cor-el - thanks. I have tried this in the past and it did not work. I did however install the latest version of Nod32 last night and the problem seems to have gone away. I had tried uninstalling/reinstalling in the past which also did not work for longer than 5 minutes. Eset must have had a bad version and the new version fixed the issue even though they claimed they did not have any issues. Dave