12030 Error Ie
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions 12030 error code you might have Meta Discuss the workings and policies of winhttpreceiveresponse failed with error 12030 this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http error 12002 developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is winhttp error 12175 a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up AJAX status 12030 up vote 2 down vote favorite I am sending an ajax XMLHttpRequest using the POST method. When the request is sent, I am getting a readyState of 4 with
Winhttp Error 12029
a status of 12030. I know 12030 is a Microsoft specific state code that indicate the connection was not sustained. However, I can't seem to find where my code would be causing this error. If I navigate to the page without using the ajax request, it loads fine. Below is the javascript method and the call line. AJAX Method /*Sends ajax request with post data that updates the content view via ajax on completion * @param message : message after completion of ajax request * @param url : url to request * @param params : post parameters as string */ function changeAjaxPost(message, url, params) { var ajx; if (window.HXMLHttpRequest) { UtilLogger.log(HtmlLogger.FINE, "Using XMLHttpRequest"); ajx = new XMLHttpRequest(); } else { UtilLogger.log(HtmlLogger.FINE, "Using ActiveXObject"); ajx = new ActiveXObject("Microsoft.XMLHTTP"); } ajx.open("POST", url, true); ajx.setRequestHeader("X-Requested-With", "XMLHttpRequest"); ajx.setRequestHeader("Content-Type", "text/html"); ajx.setRequestHeader("Content-length", params.length); ajx.setRequestHeader("Connection", "close"); ajx.send(params); ajx.onreadystatechange = function () { document.write(ajx.readyState + ":" + ajx.status); if (ajx.readyState == 4 && ajx.status =
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a
Wininet Error Codes
Full Time Job Ways to Get Help Expand Search Submit Close Search Login 12019 http error Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > winhttp error 12030 Getting rid of Ajax error number 12030 in IE Want to Advertise Here? Solved Getting rid of Ajax error number 12030 in IE Posted on 2008-05-21 JavaScript 1 Verified Solution 12 Comments http://stackoverflow.com/questions/10318865/ajax-status-12030 6,998 Views Last Modified: 2012-05-05 Hi, As you know there is a bug in IE which send request number 12030 when do ajax request, somebody suggest to get rid from this problem as this one: http://community.xajaxproject.org/viewtopic.php?id=972 (look at the last posting) is to recall the request as follow: switch(xmlHttp.status){ case 12029: case 12030: case 12031: https://www.experts-exchange.com/questions/23421667/Getting-rid-of-Ajax-error-number-12030-in-IE.html case 12152: case 12159: //repeat call here } Now the following is my code, my question is where should I place this Switch block in it and how can I repeat the call: help please var http_request = false; function makePOSTRequest(url, parameters) { http_request = false; if (window.XMLHttpRequest) { // Mozilla, Safari,... http_request = new XMLHttpRequest(); if (http_request.overrideMimeType) { // set type accordingly to anticipated content type //http_request.overrideMimeType('text/xml'); http_request.overrideMimeType('text/html'); } } else if (window.ActiveXObject) { // IE try { http_request = new ActiveXObject("Msxml2.XMLHTTP"); } catch (e) { try { http_request = new ActiveXObject("Microsoft.XMLHTTP"); } catch (e) {} } } if (!http_request) { alert('Cannot create XMLHTTP instance'); return false; } http_request.onreadystatechange = alertContents; http_request.open('POST', url, true); http_request.setRequestHeader("Content-type", "application/x-www-form-urlencoded"); http_request.setRequestHeader("Content-length", parameters.length); http_request.setRequestHeader("Connection", "close"); http_request.send(parameters); }
from GoogleSign inHidden fieldsSearch for groups or messages
The status code in the error is the status code returned by IE after our application client (browser) submits a post request. Besides the status code 12031, we've also experienced codes, 12030, 12152, etc. These codes are returned from the Windows Internet application programming (WinInet) API from windows OS. Here is a link http://support.microsoft.com/kb/193625 to see all about the WinInet error codes. Most of these error translate to something like 'client connection with the server is terminated'. Below is a screen shot of what I saw debugging using HTTPWatch. This error is not reproducible at will but is commonly reproducible after few minutes of activity on the web. This only happens with IE ( so far all versions). Supposed to be fixed in later version of IE. I can't cut and paste the image here from HTTP Watch but I will type it 00:00:51.411 2.230 0 POST ERROR_HTTP_INVALID_SERVER_RESPONSE * https://domain name/contextroot/remote/event Notice the '0' as the size of the content , the error message and the * for the content type for this request that failed. IE browser is running into issues with the HTTP 1.1 keep alive and persistent connection feature. HTTP persistent connection is the feature to reuse the same TCP connection to send and receive multiple HTTP requests/response. For more detail see http://en.wikipedia.org/wiki/HTTP_persistent_connection . The connection could be open or keep alive by a set amount of time defined by the web server and ours is set to 10 seconds in our environments. Given that there is a known bug in IE which causes the body from the POST requests to go missing if the server reset the connection -the problem may be happening when a POST request is made right before the keep-alive time-out expires and there is a slight network latency - the web server will reset the connection and force IE to resend the request. This time IE will forget to send the body(See size 0 above)