ASP.Net Timeout

Question

I am stuck with the asp.net release question with the last 2 weeks.

Scenario:

My application page has 3 controls. WYSIWYG editor (Free Textbox), text field to get the name of the article edited in the WYSIWYG editor, another text field for accepting keywords.

The order of the controls on the page is from top to bottom, as follows,
first, the Name text box
second, WYSIWYG Editor
last, Keywords text box

Problem:

When users try to save their edited documents, the IIS server returns a timeout (Production run on win 2008). But interestingly, the “Text Name” field and half of the WYSIWYG editor (it’s not exactly half, it depends on each case), the information is stored in the database. but the last "text text" is not saved. During this web server freezes for a while, kicks the user, and later after a few minutes returns to normal speed. I think the application pool has been redesigned. But everything works fine in my development environment (in My PC it works on Win 7 64bit). I also set ValidateRequest = "False" in the page directive for the development and development environment.

Environment:

.NET 4.0, ASP.NET
FreeText box WYSIWYG editor
Shared hosting windows 2008
SQL Server 2008

Trial solutions (but a breakthrough ):

I tried with different browser Firefox, chrome, IE and the same error.
ValidateRequest = "False" was added to the page directive and replaced the WYSIWYG editor with a text field and tried to save the same problem.
Just tried to register the message data directly from the page.request object. Still getting full data for the "Text field name" field for the WYSIWYG text field and nothing to rest.
There is no problem connecting a DB or a table. I checked three times.

Possible suspicions and questions:

Based on my knowledge, there are no restrictions on the length of post-data. but can I override this in IIS? I wonder if this is installed on my shared hosting.

Basically, mail message data is truncated somewhere between the browser and the server.request object. What is the reason if this happens?
If the HTTP message is truncated, why does the entire application freeze (or restart)?
What precautions should be taken when posting html content as an email message?

Thanks.

New search:

Checked my message using httpfox. The message size was about 9958 bytes. But firefox sends the first 330 bytes of data, and then the web page hangs. After about a minute, I get the error code NS_ERROR_NET_RESET in httpfox.

Checked my post using filder2 with IE9. It tries to send the first 512 bytes and then freezes. Returns "ReadResponse () error: the server did not respond to this request."

Question:

This is probably a browser or server problem. I think that if the problem is with the browser, this will not happen for IE and Firefox.

Update:

Most likely, the problem is related to web hosting. Tested by changing the URL of the form to another domain and see if you can get the values ​​in this domain. Yes it works. Only for my domain this did not work. Interestingly, I tested this for regular posting in an html page. he also did not work. Therefore, most likely, protection is installed to prevent this or incorrect server configuration. Already issued a ticket and expected.

Any ways to restore feedback helped me isolate the problem.

It is decided:

Yes, this problem was on our website. So far I have heard from them, like some firewalls blocking large mail with http. They said that now our domain is white. Anyway, now his work. But it ate 2 weeks of my time, but it was a good learning experience. Thanks guys for your help. Really appreciated.

Answer 1

I have the same error on the same web page. It was very connected, because if I used a proxy server, the error went away, if I had been called directly from my computer, I have time and never continue.

The site where this problem still appears. Dec / 2011 is http://www.auctionsniper.com/ The same site works if I switch to its mobile version.

After many checks with the above site, I found that the problem was in a very large representation! How do I find it . I save the html part of my page, because it is rendered and they start removing elements from html and making messages until I find that the message will continue when I cut out the record in the viewstate.

The solution was to disable the viewstate for many unnecessary controls and compress + reduce in smaller parts the remaining data as data in the view.

You can use Google and find many ways to compress and reduce the viewing state in parts.

Some articles:

http://msdn.microsoft.com/en-us/magazine/cc188774.aspx

how to cut his tutorial:
http://www.dotnetfunda.com/articles/article634-viewstate-patterns-in-aspnet-.aspx

how to squeeze it
http://www.hanselman.com/blog/ZippingCompressingViewStateInASPNET.aspx
http://www.codeproject.com/KB/viewstate/ViewStateCompression.aspx
http://www.google.com/search?hl=en&safe=off&q=asp.net+compress+viewstate&aq=f&aqi=g1g-b2&aql=f&oq=

Ps: In this demo page of the free TextBox that you use, the presentation space is huge! and its even empty of text, imagine how big the viewstate will be if you really have the text inside. Not so free - cost is a huge idea.

Following actions

As Jeyara talks about the comments below, it was finally a mistake, blocking large message files using a firewall on the hosting server.

Thus, the error / timeout is associated with large feedback data and a rare but existing problem.

Answer 2

Did you see what was sent back?

Try something like Fiddler2 to view the postback.

You may find that something is truncating in the browser.

The RichText area can also be limited by the number of characters it will send back.

Answer 3

Try it. In your web.config add the following

<httpRuntime maxRequestLength="8096"/> 

somewhere in the <system.web> , since the default request length is 8096, your postdata may be larger than this, so add it with a larger value than me. Hope this helps.