Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Long delays with HAProxy

  • 4 wotmołwy
  • 0 ma tutón problem
  • 42 napohladow
  • Poslednja wotmołwa wot palinst

more options

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)
Připowěsnjene fota wobrazowki

Wubrane rozrisanje

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.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (4)

more options

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.

Wot palinst změnjeny

more options

Wubrane rozrisanje

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.

Wot palinst změnjeny

more options

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

more options

"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.