Back to Support & General Questions Forum
0

Uploader multi-part form encoding seems to add an extra newline

When I set postvars: { "x": "1", "y": "2", "z": "3" }, I see the following encoding using wireshark:

CODE
------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
Content-Disposition: form-data; name="x"

1

------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
Content-Disposition: form-data; name="y"

2

------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
Content-Disposition: form-data; name="z"

3

------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ


Because of the extra newline after the "1", "2", and "3", these are seen on the server as actually having a newline after them. In theory I could trim, but what if I actually meant to have a newline at the end?

Compare this to the example on the w3.org site: http://www.w3.org/TR/REC-html40/interact/f...tml#h-17.13.4.2

by
Report Abuse
4 Replies
  • QUOTE (pulazzo @ Nov 13 2008, 08:27 AM) <{POST_SNAPBACK}>
    When I set postvars: { "x": "1", "y": "2", "z": "3" }, I see the following encoding using wireshark:

    CODE
    ------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
    Content-Disposition: form-data; name="x"

    1

    ------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
    Content-Disposition: form-data; name="y"

    2

    ------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ
    Content-Disposition: form-data; name="z"

    3

    ------YahooBrowserPlusFormBoundaryfOidA9tWEUyA5DBQ


    Because of the extra newline after the "1", "2", and "3", these are seen on the server as actually having a newline after them. In theory I could trim, but what if I actually meant to have a newline at the end?

    Compare this to the example on the w3.org site: http://www.w3.org/TR/REC-html40/interact/f...tml#h-17.13.4.2


    this is clearly a bug in the uploader corelet. Thank you for the precise report. We'll smack it by late next week.

    gordon, confirm?

    lloyd
    Report Abuse
    0
  • QUOTE (Lloyd Hilaiel @ Nov 13 2008, 10:59 AM) <{POST_SNAPBACK}>
    this is clearly a bug in the uploader corelet. Thank you for the precise report. We'll smack it by late next week.

    gordon, confirm?

    lloyd



    Yup, mea culpa. Sheepishly headed to the source...

    -- gordon
    Report Abuse
    0
  • QUOTE (Gordon @ Nov 13 2008, 04:13 PM) <{POST_SNAPBACK}>
    Yup, mea culpa. Sheepishly headed to the source...

    -- gordon


    Thanks! I look forward to the next update.
    Report Abuse
    0
  • This is fixed, but I ran into a few problems when upgrading.

    My first step was to update my application to point to 2.1.11. When I hit the application, it asked me to upgrade (I hadn't actually done it yet) and also said it would update the Uploader.

    Unfortunately, the problem with the newline persisted. I double checked it in Wireshark.

    I restarted my browser and it was still a problem.

    Then I went to BrowserPlus Preferences and it said I was still using the old Uploader.

    I went to Troubleshotting in BrowserPlus Preferences and clicked "Restart BrowserPlus"

    I went back to Firefox 3 (this is all on a Mac) and none of the BrowserPlus stuff was working, not even on your sites.

    I restarted Firefox and everything worked using the new Uploader.

    Now BrowserPlus preferences says "BrowserPlus is disabled." and "BrowserPlus not installed". Troubleshooting says "BrowserPlus is not responding: Timeout NaN seconds". I assure you that it's working in in Firefox right now.

    I know there's a lot here, so I'll try to summarize:

    1) Upgrade didn't really work for the Uploader service.

    2) It would be really great if the user-agent included the Uploader version number so that I could have seen the issue.

    3) Restart BrowserPlus from BrowserPlus preferences led to lots of little issues mentioned above, but seemed to make things work.
    Report Abuse
    0
✕ This forum is locked.
Ask a Question

Recent Posts

in Support & General Questions