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

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe

Firul de discuție a fost închis și arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Long delays with HAProxy

  • 4 răspunsuri
  • 0 au această problemă
  • 99 de vizualizări
  • Ultimul răspuns dat de SuMo Bot

mai multe opțiuni

I have a Plesk (apache) server that is behind HAProxy. When I connect securely to a web site through HAProxy using Firefox, I get long delays. If I use Safari or Chrome, the pages come right up without any delay.

If I connect to the Plesk server directly without HAProxy in the middle, there are no delays.

I do not know what would cause these delays that don't occur with other browsers.

I'm on a Mac: 115.0.2 (64-bit)

I have a Plesk (apache) server that is behind HAProxy. When I connect securely to a web site through HAProxy using Firefox, I get long delays. If I use Safari or Chrome, the pages come right up without any delay. If I connect to the Plesk server directly without HAProxy in the middle, there are no delays. I do not know what would cause these delays that don't occur with other browsers. I'm on a Mac: 115.0.2 (64-bit)

Soluție aleasă

Figured it out. It was DNS over HTTPS which is why all other browsers worked. They all use my resolver for DNS. That setting should probably not be enabled by default. The browser shouldn't do its own thing when it comes to DNS resolution without asking first.

Citește răspunsul în context 👍 0

Toate răspunsurile (5)

mai multe opțiuni

Gotcha... I will see if I can set up access for the outside world and check. Any by securely I mean HTTPS. Everything now is internal. Thank you.

mai multe opțiuni

Soluție aleasă

Figured it out. It was DNS over HTTPS which is why all other browsers worked. They all use my resolver for DNS. That setting should probably not be enabled by default. The browser shouldn't do its own thing when it comes to DNS resolution without asking first.

mai multe opțiuni

You can configure a canary domain on your network to tell software you want to use your own resolver.

mai multe opțiuni

"You can configure a canary domain on your network to tell software you want to use your own resolver."

Not "software", just Firefox, and as the link you pointed me to states, canary domains is a hack to get around another hack.

Browsers should browse. If a browser also wants to be a DNS forwarder it should not do that by default or give a warning the first time such a "feature" is added to an update and confirm the user wants their browser doing something other than what is expected and what other software was specifically designed to do. This is the kind of nonsense Microsoft does which makes their products bloated, unpredictable, and unreliable.

mai multe opțiuni

This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.