XMLHttpRequest POST readystate stalled to 1 unless Content-type is set

[miohtama]

Hi,

The topic tells it all for those who it concerns.

I came across this bug. Took 10 hours to debug. Appears on Nokia N95 8GB and probably on other Series 60 3.x phones.

For more information see:

http://orbited.org/ticket/104

Is there a public way to file bug against the browser? Not that I expected anything to happen for the issue.

[ajk]

The XMLHttpRequest spec [1] says that while using POST "authors are encouraged to ensure that they have specified the Content-Type header via setRequestHeader() before invoking send() with a non-null data argument." and application/x-www-form-urlencoded [2] is the default content type for non-binary HTTP POST.

I think this is not a browser bug.

[1] http://www.w3.org/TR/XMLHttpRequest/#send
[2] http://www.w3.org/TR/html401/interac...ml#h-17.13.4.1

[miohtama]

I think this is not a browser bug.

So hanging in the "OPEN" state without exception raised or indication given that something is wrong is considered accetable behavior?

[ajk]

Granted, it is either a browser bug or an unambiguity of the XHR spec. Surely developer should be informed of the error condition.

It seems that some versions of IE and Firefox also have similar problems as you describe if the Content-Type header is not set. So it seems this bug is not specific to S60 3.x but a wider issue across multiple browsers. Perhaps for this reason all cross-browser JavaScript libraries I've looked at set Content-Type header for XHR POST. For example jQuery, MooTools, Prototype and Dojo all default to "application/x-www-form-urlencoded".