Hello,

Receiving this after a clean installation of latest Drupal 8.x-dev on PHP 5.3.13:
[error] [client 60.29.120.35] Premature end of script headers: index.php.

Comments

Jeffrey C.’s picture

Jeffrey C. commented
Issue summary: View changes

Fixed the typo.

Jeffrey C.’s picture

Jeffrey C. commented
Title: Prevent Installation on PHP 5.3.13 » Syntax error after clean installation of Drupal 8.x-dev on PHP 5.3.13
aspilicious’s picture

aspilicious commented

It is crashing on "use Drupal\Core\DrupalKernel;" are you sure you're on 5.3.13?

Jeffrey C.’s picture

Jeffrey C. commented
Title: Syntax error after clean installation of Drupal 8.x-dev on PHP 5.3.13 » Premature end of script headers error after clean installation of Drupal 8.x-dev on PHP 5.3.13

I'm sorry, was using 5.2.17. Now that I've upgraded to 5.3.13, I got [error] [client 60.29.120.35] Premature end of script headers: index.php.

Jeffrey C.’s picture

Jeffrey C. commented
Issue summary: View changes

5.3.13 is actually greater than 5.3.3. Fixed the issue summary.

Jeffrey C.’s picture

Jeffrey C. commented

Didn't see any header output in index.php though.

aspilicious’s picture

aspilicious commented

Try a new installation and be sure your environment is ok. Are you developing for d8? Or is there a reason why you're using D8 now?

Jeffrey C.’s picture

Jeffrey C. commented

I'm using Bluehost and actually its environment should be BETTER than ok. Will try switching to another host. Not really a developer myself, just testing D8 out and trying to find some bug or error :)

droplet’s picture

droplet commented

#1651010: Unification of drupal_exit() and drupal_page_footer() and performance boost for FPM enabled environments

mondrake’s picture

mondrake
Location 🇮🇹
commented

Same problem here. Beside

Premature end of script headers: index.php

I also get a

invalid CGI ref "/500.php"

PHP 5.3.16

mondrake’s picture

mondrake
Location 🇮🇹
commented

Update to #8

Upgrading PHP to 5.4.8, everything seems to be working fine.

codewatson’s picture

codewatson commented

Had the same issues, started on on 5.2.17, couldn't get it to install, read the instructions (duh) and switched to 5.3.23, allowed me to install, but on first page load after install got "Premature end of script headers: index.php", switched to 5.4.13 and it would load.

Update: switched between the php versions just to see what would happen, and this time on the 5.3.23 I got the message "PHP's 'magic_quotes_gpc' and 'magic_quotes_runtime' settings are not supported and must be disabled." Never saw that message the first time, all I got was a 500 error. Maybe the install instructions need this listed somewhere?

Update2: Checked the 5.3.23 php ini file, and it shows both settings as "off", so.... huh?

codewatson’s picture

codewatson commented
Issue summary: View changes

Updated issue summary.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone commented
Category: Bug report » Support request
Issue summary: View changes
Status: Active » Closed (works as designed)

As stated in #9 and #10 the error was caused by using an version of Php that Drupal did not support at the time. This is not a bug as the Php requirements are stated so changing to Support Request and closing this as works as designed.