|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #134 output for Unable to open prepend file in wrong place
Submitted: 1998-03-02 23:20 UTC Modified: 1998-03-03 00:05 UTC
From: ars at ziplink dot net Assigned: rasmus (profile)
Status: Closed Package: Parser error
PHP Version: 3.0 Latest CVS OS: FreeBSD
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
24 + 33 = ?
Subscribe to this entry?

 [1998-03-02 23:20 UTC] ars at ziplink dot net
If php is unable to open the prepend file it says so, only
it says so _before_ outputing Content-Type, so the server
complains that incorrect output was recieved.

And if the server didn't parse headers, I'm sure the browser
would complain about it.

And while I'm on the subject, why do all error messages get
sent twice? Once at the top of the output, and once at the
place where the error actually occured.

I am running with debug on if that matters.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [1998-03-03 00:05 UTC] rasmus
prepend error output has been fixed.  Not sure on the double error message.  I am not
seeing that here.
 [2022-01-30 15:38 UTC]
Automatic comment on behalf of harsha14gupta (author) and web-flow (committer)
Log: Fix #134 Correct mail() argument names and docs (#159)
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jul 14 08:01:28 2024 UTC