Post a Reply
461 views

WebFileUploader test help please!

  1. 2 weeks ago

    Jay M

    Feb 8 Pre-Release Testers Austin TX
    Edited 2 weeks ago

    We have been chasing one of those bugs that just does not want to give us enough information to let us fix it.

    The problem is in the Webfileuploader. It seems to work without issue on the Macintosh regardless of the Browser (We have tested Chrome, Safari, Opera and Firefox)

    But on widows on Chrome: The file uploader stalls. The progress bar goes to 100% and the dialog is NOT dismissed.
    On Edge we can see the error code: "Internal Server Error 500"

    The app is running at: http://159.89.226.206/upload_test/

    I hate to impose on the community to do testing for me–– But I have literally spent a week And I do not have a true Windows environment That I can use regularity.

    If anyone could kindly simply try to upload file--It would be greatly appreciated. (If the dialogue That contains the Webfileuploader closes -- That means we are getting passed the bug.

    Answered by Greg O

    See post in context

    @Jay M As @Kyryl P suggested: In my case it is a known bug in Apache/ModSecurity (not Xojo). It is particularly problematic with large PDF documents.

    I would like to point out that it’s not really a bug in mod_security. It’s doing exactly what it’s designed to do.

    The issue arises from an attached file (does not have to be a pdf) having a particular sequence of characters, in this case:

    chr(13)+chr(10)+”- -“

    Followed by any ascii character. This is the exact pattern that an http post request uses to break up attachments.

    Having looked at a few offending PDF files on this case, it appears that the app that is creating these files is not properly encoding that data as simply opening the file in Acrobat Pro or PDFPenPro and saving a new file solves the issue.

  2. Olivier C

    Feb 8 Pre-Release Testers, Xojo Pro Europe (Belgium, Brussels)

    Hi Jay,

    All my tests are OK, meaning the Webfileuploader windows closes after uploading.
    Note that both Windows machines are running in VM (Parallels Desktop) on macOS Mojave.

    Details:
    Windows 7 (Family Edition, SP1):
    . Google Chrome 71.0.3578.98 (64 bits) --> OK
    . Firefox 65.0 (64 bits) --> OK

    Windows 10 (Family edition, 64bits) :
    . Google Chrome 72.0.3626.96 (64 bits) --> OK
    . Firefox 65.0 (64 bits) --> OK

  3. Roger S

    Feb 8 Gaspé, Québec, Canada

    Tried on Win 10 and FireFox and it doesn't close.... (Parallels desktop VM on Mojave)

  4. Roger S

    Feb 8 Gaspé, Québec, Canada

    Edge works fine here

  5. Hal G

    Feb 8 Pre-Release Testers, Xojo Pro, XDC Speakers Orlando, FL
    Edited 2 weeks ago

    Just tested:

    • Mac Chrome. Worked fine as you stated.
    • Windows 10 Chrome 70.0.3538.110 worked but the progress bar went to 100% then to about 75% and then seem to finish.
    • Edge worked fine.

  6. Jay M

    Feb 8 Pre-Release Testers Austin TX

    FWIW WE found this in the Xojo cloud error logs. I have no clue how to read it.

    5310 [Fri Feb 08 16:21:15.653718 2019] [:error] [pid 5655] [client 73.196.148.120:60548] [client 73.196.148.120] ModSecurity: Access denied with code 44 (phase 2). Match of “eq 0” against “MULTIPART_UNMATCHED_BOUNDARY” required. [file “/etc/httpd/conf.d/mod_security.conf”     ] [line “34"] [id “200003”] [msg “Multipart parser detected a possible unmatched boundary.“] [hostname “159.89.226.206”] [uri “/upload_test/index.cgi/8623FFEE06AA5C966FB5EF07B9B01D36479CEA56/upload”] [unique_id “XF2se4Jmw3UZy4B3mie2NwAAAAQ”], referer: http://159.89.2     26.206/upload_test/

  7. Roger S

    Feb 8

  8. David C

    Feb 8 Pre-Release Testers, Xojo Pro Derby, ITM

    Safari on macOS MoHarvey worked OK

  9. Jay M

    Feb 9 Pre-Release Testers Austin TX

    Thanks all: I have created a case if anyone is looking at the same issue:

    Feedback: 54882

  10. Kyryl P

    Feb 9 Pre-Release Testers, Xojo Pro Europe (Ukraine)
    Edited 2 weeks ago

    It looks like XojoClouds mod_security goes crazy on some Windows clients.

    There are some messages that it can have “False positive“ catches

    https://github.com/SpiderLabs/ModSecurity/issues/652
    https://github.com/SpiderLabs/owasp-modsecurity-crs/issues/827
    https://github.com/SpiderLabs/ModSecurity/issues/1804

    Wrote the same to the Feedback case

  11. Jay M

    Feb 9 Pre-Release Testers Austin TX
    Edited 2 weeks ago

    @Roger SArneault Edge works fine here

    Rodger 2 questions:

    1. Can you upload a very big PDF?
    2. Are you on a true PC or a virtual instance.

  12. Greg O

    Feb 9 Xojo Inc

    @Jay M Rodger 2 questions:

    1. Can you upload a very big PDF?
    2. Are you on a true PC or a virtual instance.

    Jay, what do you consider “very big” ?

  13. Jay M

    Feb 11 Pre-Release Testers Austin TX
    Edited 2 weeks ago

    @Greg OLone 8 Megs fails on Xojo cloud.

    We are now running the exact same code with the exact same PDF on AWS (as a test) and it does not fail.

  14. Kyryl P

    Feb 11 Pre-Release Testers, Xojo Pro Europe (Ukraine)

    On AWS we have nginx + standalone 64bit app inside docker container, and it works fine.

  15. Roger S

    Feb 11 Gaspé, Québec, Canada

    Sent a 6 Mo PDF and the window did not close on Edge.

  16. Roger S

    Feb 11 Gaspé, Québec, Canada

    Sent a 48 Ko PDF and doesn't close...

    Edge worked las time...

  17. Roger S

    Feb 11 Gaspé, Québec, Canada
    Edited 2 weeks ago

    Tried again with Firefox and worked fine. (48 Ko)

  18. Roger S

    Feb 11 Gaspé, Québec, Canada

    Tried the 6 Mo with Firefox. Works

  19. Roger S

    Feb 11 Gaspé, Québec, Canada

    Tried again with Edge with 6 Mo and works....

  20. Michael D

    Feb 11 Pre-Release Testers, Xojo Pro

    I'm suspicious of WebFileUploader - see this bug report for example: Feedback Case #53053

  21. Newer ›

or Sign Up to reply!