Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Problems with loading website since Firefox vers 21. How does FF handle "DNS loadbalanced" websites?

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 2 Hecha
  • Mbohovái ipaháva hape

hape
hape
more options

We are hosting a webapplication on a DNS loadbalanced infrastructure. Two identical reverseproxies are forwarding incoming requests to two identical webservers. But each proxy forwards to only one webserver. Not crosswise though. All systems are windows 2008R2 servers with IIS7. The website works well with IE, Chrome and Safari, but not with Firefox since version 21. We found as a reason, that the requests send from FF are switching between both webservers, instead of keeping the server during the established session. As a workaround, we can delete the "Active Login" cache on the Firefox client, which helps until FF is restarted. Although I don't see the correlation between these, this is a reproducable behaviour. After deleting the "Active Login" cache, all the requests reach one single webserver. The application is a silverlight application, which might be good to know. Has anyone seen such a behaviour, and ... even more important.. can anyone help with a solution or at least an explanation? Thanks!

We are hosting a webapplication on a DNS loadbalanced infrastructure. Two identical reverseproxies are forwarding incoming requests to two identical webservers. But each proxy forwards to only one webserver. Not crosswise though. All systems are windows 2008R2 servers with IIS7. The website works well with IE, Chrome and Safari, but not with Firefox since version 21. We found as a reason, that the requests send from FF are switching between both webservers, instead of keeping the server during the established session. As a workaround, we can delete the "Active Login" cache on the Firefox client, which helps until FF is restarted. Although I don't see the correlation between these, this is a reproducable behaviour. After deleting the "Active Login" cache, all the requests reach one single webserver. The application is a silverlight application, which might be good to know. Has anyone seen such a behaviour, and ... even more important.. can anyone help with a solution or at least an explanation? Thanks!

Opaite Mbohovái (2)

cor-el
cor-el
  • Moderator
more options

A good place to ask advice about web development is at the mozillaZine "Web Development/Standards Evangelism" forum.

The helpers at that forum are more knowledgeable about web development issues.
You need to register at the mozillaZine forum site in order to post at that forum.

hape
hape Porandu apoha
more options

Thanks cor-el for that hint. I will ask my question there too. I thought it's not necessarily connected to the application as with IE and other browsers there is no problem. We also mentioned that with some internet providers it works even with firefox. So, for me it looks as it is connected to DNS resolution. Proxyserver in Place or not at provider side, or s.th. like that.