Φόρουμ κοινότητας «Firefox»

all the sights I've used for years will not open and will not work I can't even use them any more they work fine in other browsers don't know what you did but it is almost unusable

bold text When I try to go to my "FIREFOX" it answers me in French of course but here you don't accept to write me in French and so it's very difficult for me ... (could you help me for this of course ???) : "hmm this adress doesn' seem to be valid." Hum, cette adresse ne semble pas valide.

What must I do please ??? [edited from public] @orange.fr

i want to access www.fintreeindia.com i pursue professional courses that's my class website and also i could not access youtube also my exam are nearly

Hello everyone,

We are currently investigating an issue where browsers are sending HTTP requests with Connection: close in the header during integrated Windows authentication (NTLM authentication) via SAML Service Provider (SP), leading to premature termination of the TCP connection.

This behavior occurs in the middle of the authentication process, preventing the NTLM authentication from completing and subsequently prompting for re-authentication.

We have observed the following browser behaviors:

Chrome and Edge: These browsers function without issues, communicating with Connection: keep-alive. Safari (macOS): Older versions of macOS with Safari exhibit the Connection: close behavior, leading to authentication failure. Newer versions of macOS with Safari work correctly with Connection: keep-alive. Firefox (macOS): Even on the latest versions of macOS, Firefox continues to attach Connection: close, resulting in authentication failure. Upon reviewing logs, we've identified that various browsers attach the Connection: close header during the NTLMSSP_NEGOTIATE request in the NTLM authentication sequence. Although this happens in an environment with a load balancer, we have confirmed that the load balancer is not modifying the header; rather, the client (browser) is adding it.

We would appreciate your insights into the conditions under which Firefox attaches Connection: close to HTTP requests, especially considering the differences across macOS versions and other browsers, addressing the following points:

Are there any known conditions or past cases where Firefox outputs Connection: close in an NTLM authentication environment via SAML SP? Given that older Safari versions show similar behavior, we are also considering if there's a common factor depending on NTLM authentication and browser version. What are the general heuristics, logic, or triggers for a browser to decide to "close" a connection or to attach Connection: close? We are particularly interested in cases that occur mid-authentication process. Could specific configurations (e.g., the combination of SAML and NTLM authentication, or the presence of an intermediate proxy/load balancer) potentially influence Firefox's Connection: close behavior? Are there any additional logs or debugging information we should collect from the Firefox client side to further pinpoint this issue? Any guidance or suggestions you could provide to help us resolve this problem would be greatly appreciated.

Thank you.

I need help with a problem that has tortured me for weeks. I use debian 13 with plasmakde. I don't know why, but when I connect to a wifi after some time it doesn't work anymore ONLY with Firefox. I can perfectly use any other app which requires internet but firefox. Sometimes it gives me the error "The connection has timed out", sometimes the error "Unable to find the proxy server" (even if I selected no proxy in the network settings). I searched online but I couldn't find anything helpful, so I can only hope to find a solution in here. Thank you very much in advance!

While browsing on my desktop , I am unable to open E Shram Card blog. it appears like there is an error in connection , but despite of good connection, cannot open it.

I just started up my new MacBook Pro, M5 pro machine and Firefox will not work. Tahoe 26.3 is OS.

Dale Howard Jonesboro, GA

PS--Safari and DuckDuck Go browsers are working normally.

The connection has timed out

The server at eofficepwd.kerala.gov.in is taking too long to respond.

   * itemThe site could be temporarily unavailable or too busy. Try again in a few moments.
   * If you are unable to load any pages, check your computer’s network connection.
   If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.