"The connection was reset" in Firefox only on postbacks - asp.net

I'm getting an error message of "The connection was reset" in Firefox on my ASP.NET site. Here are the details:
doesn't work in Firefox 11, 12, and 14 though appears to 3.6
happens everywhere on site where there's a postback
the message comes up in under a second after doing the POST
works in Chrome and IE
works locally
view state is relatively small
the pages are not performing long operations (e.g., file upload)
I've tried clearing the cache and running Firefox in safe mode, but it makes no difference.
Any help would be greatly appreciated!

Close all of your anti-virus software and restart your FF.
See solution of connection was reset for more help.

Related

Chrome waiting for available sockets, Firefox is fine

We have a Wordpress based website (rendeljkinait.hu), and we face freezing issues while editing articles when using Chrome. When I hit the save button for the 7th time without page reload, the article editor freezes during save and I get "waiting for available socket" error in Chrome. No matter how long I wait, the editor won't save until I reload the page. When I'm using Firefox, everything is fine, no matter how much I hit the save button. Current Wordpress version is 5.2.3, but error occured in former versions too.
I investigated the error, and found it is caused because Chrome never closes the open sockets until I reload the page. So until hitting the button 6 times everything is fine, since Chrome and other modern browsers allow to have maximum 6 paralell connection to a single host. But after I press the button for the 7th time, there is no space for another connection, so Chrome is waiting for the older connections to get closed, but it never happens.
Here's a screenshot from net log
Using Firefox I observed that it always closes the connection after the save is successful, so only 1 connection is active all the time, it never exceeds the 6 paralell connection limit. I attached Chrome netlog file here, you can view it here. I also attached a video showing Firefox closing the connection here (107.6.*.** is our servers IP).
For various reasons we have to use Chrome, so I would like to find a solution for this problem, but I'm completely stuck. Does anyone have a suggestion what could cause the problem and how to solve it?
Thanks in advance!
I have the same problems with chrome and gutenberg.
It is impossible to do any heavy editing on the site, so I use firefox for all admin related stuff.
Haven't found a solution either...
For anyone who might find this topic with similar problem: seems like it was a Wordpress bug, a Wordpress update solved the issue.

Server Error in '/' Application (only in Firefox)

I have a bit of a brain teaser. I am getting the attached server error when I load ANY page on my website. However, this ONLY happens in Firefox. Any other browser loads the page just fine. I have cleared my cache and have completely uninstalled and re-installed FireFox to no avail. Any idea why a server error would only show up in certain browsers? This is a windows based machine running IIS. I'm totally stumped. Thanks!
It's hard to see the exception type because the text is so small on you resized image.
Have you tried monitoring the request using Fiddler, or launching FF Dev tools (CTRL+SHIFT+I from FireFox)? Is there anything in that output that could reveal a clue?

Internet Explorer issue - cant load content

I'm designing a web app in asp.net WebForms.
Everything is working OK on all browsers except IE [all versions]
I can load the site and browse it on IE, but eventually, when trying to browse further, IE just can't load content:
message from Fiddler:
1360 Content-Length mismatch: Request Header indicated 13 516 bytes, but client sent 0 bytes.
I can see that IE is trying to download content, but nothing is sent from server.
It eventually ends up in Connection timeout error.
At the same time, the IE instance that causes problem can load up any other website flawlessly
The problem dissapears after closing IE and opening it again, but returns after a while.
Although I don't think that it's a cause of the problem, it maybe important: My app uses signalR.
I ran out of ideas, and that's why I'm asking, because maybe you guys have some directions where to look and what to check.
thanks.

Wordpress site under windows XP - appears to be many problems

Would someone mind looking at this fairly basic (I thought) site that I've built for my father?
www.pws-consulting.com
It loads up fine and works under the latest version of chrome, firefox, safari on my mac, and does the same on windows 7, even in ie. (though some of the css dies, which is acceptable).
On his windows xp machine however, the site has many problems.
Explorer browser.
Upon initially accessing the website, the following error message appears "Internet Explorer encountered a problem and needs to close".
When I hit "Don't send" for the error report, the tab for the website is recovered and it reopens. Pics and text content look ok.
However for every hyperlink (Services, Contact, etc), the same error message above appears.
Eventually the browser crashes.
Firefox browser:
Website opens normally but all text content is mispositioned at the bottom of each page, hyperlinks repeat, colour map does not appear, etc.
All-in-all, a formatting mess.
I've used AdobeBrowser Lab to test the site and it appears to be finder going back to IE 7, Firefox 5.0 on windows so I'm at a lose to understand what is wrong.
Thanks in advance for any help. All the best to everyone in this new year.
Cam
Doesn't seem to crash on WinXP IE 6.0 for me. Works great on IE 7+ though. No problems in Firefox, Chrome, Opera, Safari either. Must be an issue with your computer? Did you try another computer?

Internet Explorer 8 timeout too quick on page POSTs

We have an asp.net site running, which has been working fine for some time, but recently I have been experiencing some issues with IE8.
On posting some pages - mainly on our development server, although on staging too - we get an occasional "Internet Explore cannot display the webpage" error along with the button asking to diagnose connection problems. IE only seems to wait 10 seconds before timing out. I know that the page itself may take longer to load the first time (on dev and staging). So press F5 and everything then works fine.
Is there anything that should be done in the aspx page to tell IE to wait a bit longer?
I thought I had read that the default timeout supposed to be 90 seconds or something for browsers.
A bit more info:
It mostly happens on a POSTing a signup page, but that is just because I test that page and it starts the IIS App, makes the first connection to SQL and pre-caches some information. That first time the page can take 10-15 seconds to come back. IE8 times out after 10 seconds as it has had nothing back.
This happens on a dev W7x64 machine with 8GB RAM, as well as on a staging server WIN2008.
Having googled around a bit, some people are seeing the same problem, but no conclusive pointers to the problem or a solution.
It isn't a connection problem; everything works fine in Firefox, Chrome and even IE7; I have tried with add-ons disabled and resetting IE settings, still happens.
Ideas welcome.
Try this out
<httpRuntime executionTimeout="15"/> under system.web in the web.config
A 10 second timeout might be a usability tool in disguise. 10 seconds is a pretty long time. Js capable browsers are > 99% now, why not push it off over Ajax and poll until the long work is done, then redirect to the next page? You could show the user more useful progress info in the meantime. If for some reason the next page itself is the source of the slow down and cannot be separated from its slow parts, you could finish by precaching the next page then redirecting.
Check your Application pool Advanced settings in IIS. It may be lower than is normal. Maybe the Ping period? Mine is 30secs
I think that the long term solution is not actually related to timeout configuration.
You're saying that only the first request takes a long time, and it takes > 10 seconds, so you should issue a warm-up request first after installing your application in a way that the first request load is never experienced by the end user.

Resources