×

Discussion Board

Results 1 to 4 of 4
  1. #1
    Regular Contributor
    Join Date
    Jan 2004
    Location
    Helsinki
    Posts
    376

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

    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.
    Mikko Ohtamaa

    http://mfabrik.com
    http://blog.mfabrik.com

  2. #2
    Nokia Developer Expert
    Join Date
    Dec 2007
    Posts
    14

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

    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

  3. #3
    Regular Contributor
    Join Date
    Jan 2004
    Location
    Helsinki
    Posts
    376

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

    Quote Originally Posted by ajk View Post
    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?
    Mikko Ohtamaa

    http://mfabrik.com
    http://blog.mfabrik.com

  4. #4
    Nokia Developer Expert
    Join Date
    Dec 2007
    Posts
    14

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

    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".

Similar Threads

  1. Recording in Amr Format
    By losym in forum Symbian Media (Closed)
    Replies: 12
    Last Post: 2009-03-26, 06:41
  2. D211 with RH7.3
    By fiveam in forum Multimodecards
    Replies: 3
    Last Post: 2003-02-24, 09:06
  3. Audio content type
    By abhishekgupta in forum General Messaging
    Replies: 2
    Last Post: 2002-07-24, 07:19
  4. How Set Content type
    By Nokia_Archive in forum Browsing and Mark-ups
    Replies: 1
    Last Post: 2002-05-14, 18:33
  5. Problem with Nokia D211 Linux Drivers
    By fiveam in forum Multimodecards
    Replies: 1
    Last Post: 1970-01-01, 02:00

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×