Hi Gravity Forms team,
We're having a problem with a 500 internal server error on a pretty simple form. The error it returns in our site log is the following:
Premature end of script headers: php-legacy, referer: http://protectourdefenders.com/get-involved/
That is the url of the form that returns the error after filling it out if you want to see for yourself. I looked on the forums and came up with the following post from a while ago:
http://www.gravityhelp.com/forums/topic/premature-end-of-script-headers-error
Looks like the person posting wasn't able to consistently reproduce the issue in that case. In my case, unfortunately it's all too easy to reproduce the error.
A few other things that may help:
- Entries are recorded in the Gravity Forms backend but email notifications are not sent. I have it set to return some text after the form is filled in, rather than redirect to another page.
- I'm using a BuddyPress-modified theme but I tried previewing the form using the Gravity Forms preview function as was suggested in the thread referenced above but unfortunately the error comes up there too so I doubt it's a theme-related issue.
- I was able to test the form and it worked perfectly once with email notification going through fine and the message after filling it out displayed fine. However after changing the email address that it notified, the problem started.
Update 1: The plot thickens...
I just tried changing the email notification back to the original address which had worked when I tested it once. It appears that it works fine when sending to a Gmail account but we're getting the error when the notification address is set to another email address the internal server error is given consistently.
For what it's worth the email address that doesn't work is routed through Google Apps for Domains, though I have no idea why that would make a difference since it's just a normal email address for anyone who doesn't know what it really is.
Update 2: after trying with another Gmail address it seems to work fine in terms of not returning the error. With no notification email the form works fine too.
Trying with an obviously incorrect email for the notification address (i.e. asdflkjalk@gmail.com) returns the same internal server error.
It would appear that an incorrect notification email address causes the form to return that nasty 500 Internal Server Error.
Update 3: After it working for several minutes, with no changes made it has stopped working again unfortunately with a Gmail notification address that worked before. After trying it several minutes later it seems to work again. At first we thought it was an issue with it rejecting duplicate entries (even though we don't have that option checked) but when trying it out with completely new information it still sometimes returns the error.
