WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 8 years ago

#2418 closed defect (bug) (invalid)

500 error when viewing site, no 500 error when viewing admin pages

Reported by: pauljmartinez Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.0.1
Component: General Keywords: 500 error index 2.0.1 installation malformed header
Focuses: Cc:

Description

Brand new install of 2.0.1, PHP Version 4.2.3, Apache/1.3.33 (Unix) mod_tsunami/3.0 FrontPage/5.0.2.2634, at Hostway (http://www.hostway.com).

All of my admin, configuration, dashboard, writing, and managing screens work fine. If I try to view the site I get a 500 error regardless of the selected permalink structure. Have tried deleting the .htaccess and resetting the permalink structure.

Most intersting issue seems to be that the 500 error only appears when actually viewing the site, no problems accessing the admin pages.

Have seen a little talk that it may be due to the code writing a bad header that the server does not like. "HTTP/1.1 200 ok"

Change History (5)

comment:1 pauljmartinez8 years ago

  • Keywords malformed header added

Here is the error I am receiving when trying to view the homepage of the blog.
http://www.flickerbox.com/blog2/

[Tue Feb 21 12:05:18 2006] [error] [client 66.123.77.166] malformed header from script. Bad header=HTTP/1.1 200 OK: /www/flickerbox/cgi-bin/php

comment:2 pauljmartinez8 years ago

I added a post to the support forum to see if I can get some more information.
http://wordpress.org/support/topic/62057

comment:3 war593128 years ago

I just got this too and it tunned out that WordPress 2.1-alpha2 creates a bad .htaccess file atm when there is not an extra line break at the end. It just attaches itself to the last char on the current line which causes 500 server error.

comment:5 foolswisdom8 years ago

  • Milestone 2.0.1 deleted
  • Resolution set to invalid
  • Severity changed from blocker to normal
  • Status changed from new to closed

Closing bug as invalid.

It has not been updated with additional information in many months, particularly in light of chradil@… identifying what may have been the origin of the problem.

Note: See TracTickets for help on using tickets.