Bug 21585

Summary:

XMLHttpRequest status code is zero for time-consuming POST request

Product:

WebKit

Reporter:

CHENG Fu <alexcheng1982>

Component:

WebCore JavaScript

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED DUPLICATE

Severity:

Normal

CC:

Priority:

Version:

525.x (Safari 3.1)

Hardware:

Mac (Intel)

OS:

OS X 10.5

Attachments:

Description	Flags
The source code of my testing servlet	none
HTML file to test the servlet	none

CHENG Fu

Reported 2008-10-13 20:11:18 PDT

I used a HTTP POST request to fetch data from the server-side. Once the processing time in the server-side is long, say 4 mins, I got a xhr error in the browser side with status code is zero. I tried dojo and jQuery's xhr library. Both have the same problem. I'm wondering if there exists a hidden timeout setting in WebKit.

Attachments
The source code of my testing servlet (2.52 KB, text/plain) 2008-10-13 20:12 PDT, CHENG Fu	no flags	Details
HTML file to test the servlet (1.24 KB, text/html) 2008-10-13 20:15 PDT, CHENG Fu	no flags	Details
View All Add attachment proposed patch, testcase, etc.

CHENG Fu

Comment 1 2008-10-13 20:12:52 PDT

Created attachment 24335 [details] The source code of my testing servlet

CHENG Fu

Comment 2 2008-10-13 20:15:30 PDT

Created attachment 24336 [details] HTML file to test the servlet

CHENG Fu

Comment 3 2008-10-13 20:16:05 PDT

Add two attachments of my test

Alexey Proskuryakov

Comment 4 2008-10-16 00:53:57 PDT

Does this still happen for you with recent nightly builds from <http://nightly.webkit.org>?

CHENG Fu

Comment 5 2008-10-16 01:09:32 PDT

I tried the recent daily build (version 528.5+). It doesn't has the problem.

CHENG Fu

Comment 6 2008-10-16 01:30:49 PDT

But WebKit(version 525.x) is shipped with Safari 3.1, which is one of the target browsers of my application. I can not reduce the processing time in the server-side. I also tried to use PUT instead of POST, the same problem occurred. But the GET method is OK. Could you please suggest some workarounds for me to support Safari 3.1? It seems that I can only change the HTTP method from POST to GET. BTW: Safari 3.1 on Windows and Firefox 3 on Mac don't have this problem.

Alexey Proskuryakov

Comment 7 2008-10-16 02:16:13 PDT

For a workaround, dummy keep-alive responses can be sent from the server. This will help with proxies closing connections because of timeout, too. *** This bug has been marked as a duplicate of 19758 ***

Note You need to log in before you can comment on or make changes to this bug.