ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

"Internal Server Error" on quick save

March 24, 2013 12:58pm

Subscribe [1]
  • #1 / Mar 24, 2013 12:58pm

    justred.ca

    23 posts

    I’ve been asked to help with a site running ExpressionEngine 1.7.3, the site owner recently started encountering problems when trying to save one of their content entries. When pressing the “Quick Save” or “Update” button for this particular entry, they get a 500 internal server error.

    This doesn’t appear to be happening when saving any other entry on the site. In case some of the data for the entry was causing a problem, I also went back and created a new entry to see if I could narrow it down. I had a bit of luck with that, but still didn’t find any real rhyme or reason to the problem - the channel contains a body field and if that field has more than 67 lines of text AND the text past line 67 contains a named anchor (<a name=”“>), then the error occurs. Otherwise, I can save the entry without a problem.

    It’s probably also worth noting that the same error occurs if I try to save the same content using a template.

    As best I can determine, it appears to be a server-related issue - though when I contact the hosting provider (dotCanada.com), they of course tell me that it must be a software issue (more on that below). I have tested by copying the site (the files & database contents) to 4 other servers and the problem does not occur with any of them.

    Any ideas what the problem might be, or suggestions for troubleshooting it?

    (As a quick aside, the dotCanada.com support staff haven’t been much help so far. They’re insisting that it’s a problem with ExpressionEngine, even though I’ve provided them with verifiable proof that the issue does not occur on 4 other servers.)

  • #2 / Mar 24, 2013 4:36pm

    justred.ca

    23 posts

    A quick update: it’s definitely a server issue, and I think I’ve tracked down the exact cause. I’ll briefly summarize the details here, for anyone else in the same boat - hopefully it will save you a few hours of trying to troubleshoot someone else’s servers for them.

    I did some more testing and it appears that the issue has nothing to do with EE - I setup a basic static HTML page with a form, and I get the exact same error when I submit the same data that was causing a problem in EE. And when I changed the form’s method to GET instead of POST, I got a “Request-URI Too Large” error (instead of the “Internal Server Error”).

    Researching that error lead me to these pages:

    https://confluence.atlassian.com/display/JIRAKB/Long+URLs+Are+Rejected+by+Apache+with+‘Request-URI+Too+Large’+Error
    http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestline
    http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestfieldsize

    Of course, it only helps if your host is willing to increase those limits… though at this point, hopefully they’ll stop with the “we’ll just blame some component we’re not responsible for” games.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases