XmlHttpRequest starts failing intermittently with status 0 with Chrome version 44

764 views
Skip to first unread message

Mandy Shen

unread,
Aug 21, 2015, 6:05:15 PM8/21/15
to Chromium-discuss
We start seeing the following stack trace very often with recent version of Chrome (version 44) from our GWT app. There is no change in our app. IE and FF seem to be fine. Any idea?

In the console, I saw many "net::ERR_INSECURE_RESPONSE" were reported. And there are also a warnings about Mixed Content.
"Mixed Content: The page at 'https://<url>' was loaded over HTTPS, but requested an insecure plugin data 'http://<url>/soap'. This content should also be served over HTTPS."

With Chrome version 44, the requests start failing from time to time, but not all the time.

In "Network" panel, the status for the failed request is shown as "(failed)", the request type is "xhr".

SEVERE: CLIENT EXCEPTION: com.google.gwt.user.client.rpc.StatusCodeException: 0
java.lang.Throwable: 0
at com.google.gwt.core.client.impl.StackTraceCreator$CollectorEmulated.$fillInStackTrace(StackTraceCreator.java:174)
at java.lang.RuntimeException.RuntimeException(RuntimeException.java:508)
at com.google.gwt.user.client.rpc.StatusCodeException.StatusCodeException(StatusCodeException.java:35)
at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.$onResponseReceived(RequestCallbackAdapter.java:209)
at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:258)
at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:412)
at Unknown.anonymous(XMLHttpRequest.java:351)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java:189)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:242)
at Unknown.anonymous(Impl.java:70)

Phil

unread,
Sep 8, 2015, 11:34:18 AM9/8/15
to Chromium-discuss
We have also been seeing this intermittent issue. We use Ajax call to test the readiness of the application. Always over HTTPS using a self-signed certificate that the user has already agreed to. Most of the time the mechanism works fine. Every now and then the Ajax calls fail with net::ERR_INSECURE_RESPONSE. Seems to be a bug.

Phil Sladen

unread,
Sep 16, 2015, 6:59:29 AM9/16/15
to Chromium-discuss
Actually, for us this issue was due to our SSL certificate being updated in the background by one of our processes. So, not a browser issue.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

Reply all
Reply to author
Forward
0 new messages