1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Fixed Web server filesize limit causes "undefined" error

Discussion in 'Resource Manager Resolved Bugs' started by Kent, Mar 26, 2013.

  1. Kent

    Kent Active Member

    The uploader detects PHP's upload limit, but not the web server's limit.

    If the web server's file upload size limit is lower than XenForo's, it causes the uploader to just return an error "undefined."

    JS console produces this after a few upload progress updates:
    Uploaded 8060928/11290580 bytes.
    Upload failed: [Object { creationdate=Date,  size=11290580,  type=".zip",  more...}, -220, "Error #2038"]
    All files uploaded.
    Reproduce: try to upload a larger file than allowed by the web server.

    With Nginx:
    client_max_body_size 1m;
    Nginx responds with HTTP 413 (Request Entity Too Large)
    Weppa333 likes this.
  2. Weppa333

    Weppa333 Active Member

    was gonna open the same :)
  3. Kent

    Kent Active Member

    I did the same with a post attachment and got the error "There was a problem uploading your file."
    Although that's better than "undefined" perhaps it should check the returned HTTP code to determine that the upload failed because the webserver rejected the request because it was too large.
  4. Mike

    Mike XenForo Developer Staff Member

    The "undefined" error has been fixed.
    Liam W, Jon W and Kent like this.
  5. xenTheory

    xenTheory Active Member

    In which release? It's still happening on 1.1.4
  6. Jeremy

    Jeremy Well-Known Member

  7. xenTheory

    xenTheory Active Member

    Yep just saw this was RM related but from what I can see it gives an error message now but the actual issue is not fixed, or do uploads work correctly now?
  8. xenTheory

    xenTheory Active Member

    Was correct, it's replaced with a proper message but the error still persists.
  9. Kent

    Kent Active Member

    The error cannot be corrected by the Resource Manager, you must change the web server configuration to raise the limit.

Share This Page