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.
Related
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.
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?
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.
Our website is an ASP.net 4.0 webforms website using AjaxControlToolkit. It was online in the last week without a problem but since today one of our clients is receiving an 'HTTP Error 400. The size of the request headers is too long' when accessing the site from Firefox. It works in IE. Looking at the logs I see requests with really long junk attached after the URL:
...Statistics.aspx?_TSM_HiddenField_=ctl00_scriptManager_HiddenField&_TSM_CombinedScripts_=;;AjaxControlToolkit,+Version=4.1.51116.0,+Culture=neutral,+PublicKeyToken=28f01b0e84b6d53e:de-DE:fd384f95-1b49-47cf-9b47-2fa2a921a36a:475a4ef5:effe2a26:8e94f951:1d3ed089:addc6819:
5546a2b:d2e10b12:37e2e5c9:5a682656:c7029a2:e9e598a9
The URL should simply be .../Statistics.aspx.
I have found the problem: there were too many cookies on the site. Removing them solved the issue.
The problem had nothing to do with AjaxControlToolkit. Sorry for misleading the community with irrelevant details.
Edit:
I personally have cleaned the cookies using the Firecookie plugin for Firebug in Firefox but you can clean your cookies by pressing Ctrl+Shift+Del and selecting 'Cookies'.
I have recently experienced some strange caching issues with Google Chrome. I have a website serving several JS and CSS files with far future expiration dates. Sometimes, Chrome would fail to load one of the files (usually our biggest JS file, but sometimes another), and a page Reload / Force Reload / browser restart do not help. The only way to get rid of the problem is to completely clear the browser cache.
I used the Chrome developer tools and noticed that Chrome is requesting the file with the following headers:
If-Modified-Since:Thu, 14 Apr 2011 19:09:29 GMT
Range:bytes=41681-41681
to which the server responds with a "304 Not Modified" status. The developer tools then list the file size a 0 bytes.
The interesting thing is that 41681 is the actual length of the page (after compression), and Chrome is strangely trying to request the next byte after the end of the file.
I used the Chrome "about:net-internals" page to examine the cache and found that the file is indeed cached but is mysteriously flagged as "RESPONSE_INFO_TRUNCATED". Other than that, the cached content look perfectly fine (I compared it with a working copy of the cached file).
I have searched all over the web and the only reference I could find to such problem is on Meta: https://meta.stackexchange.com/questions/89224/does-anyone-have-problems-viewing-so-in-chrome-11
The issue reported there sounds a lot like the problem we are having but there are no conclusions other than that clearing the browser cache is a temporary solution. That post is almost two months old, and several versions of Chrome have been released since and the problem still exists.
The only relevant Chrome bug that I found is this one (reference the meta post): http://code.google.com/p/chromium/issues/detail?id=62712. However there was no activity on this bug since it has been reported.
I am very curious whether anyone else experienced similar issues, and whether anyone has any idea about what might be causing this.
Thanks,
Sagi