This page contains the following error: error on line 1 at column 1: Document is empty

This page contains the following error: error on line 1 at column 1: Document is empty

  1. Blog
  2. 15 November 2026
  3. 4 min read

Stefan Bogdanescu

Founder & Senior Architect

Debugging "Document is Empty" When Outputting XML from PHP

When a browser reports error on line 1 at column 1: Document is empty, it usually means the HTTP response body contains zero bytes before the parser attempts to read the first character of an XML declaration. In your specific case, this happens because PHP sends headers and begins buffering output before any valid data or whitespace is written to the output stream, causing the browser to interpret the initial silence as an empty document.

The Root Cause: Premature Output

In your connect.php file, you have this line:

echo "connected succesfully";    

This sends a string of text directly to the browser immediately after the database connection is established. Even though your main script (connect.php is included via require_once), PHP's output buffering might not be active yet, or the headers from the main script haven't been sent when this echo executes. More critically, if connect.php outputs anything before you set the Content-Type header in your main script, that text gets mixed into the response body.

However, the specific error "Document is empty" often points to a different issue: Whitespace before the XML declaration.

In your main script, you have this sequence:

  1. You connect to the database.
  2. You run the query.
  3. You check if ($result->num_rows > 0).
  4. If there are no results (else block), you echo "0 results".
  5. Finally, you set header ("Content-Type:text/xml").

If your database table projet is empty, the code enters the else block and executes echo "0 results";. This prints a string to the output buffer. Immediately after that, you set the header and try to print the XML structure. The resulting HTTP response body starts with the text 0 results, not an XML declaration like <?xml version="1.0"?>.

While browsers are forgiving of text before XML declarations in many cases, strict parsers or specific server configurations might reject this as malformed. But the real culprit for the "Document is empty" error in your scenario is likely the order of operations regarding headers and output.

You set header ("Content-Type:text/xml") after potentially echoing data (in the else block) and after including files that echo data. If any whitespace (newlines, spaces, indentation) exists between <?php and the first executable code in your file, PHP will send those bytes to the browser before the headers are finalized.

Correcting the Flow

To fix this, you must ensure that no output occurs before the XML declaration. Here is the corrected logic flow:

  1. Include config: Load connect.php.
  2. Check connection: Ensure $conn exists and no error occurred.
  3. Run Query: Execute the SQL.
  4. Generate XML: Create the root node and populate it. If there are no rows, decide how you want to represent that (e.g., an empty list or a specific status element), but do so within the XML structure, not with raw echo.
  5. Set Headers: Call header("Content-Type: text/xml") immediately before outputting anything else.
  6. Output XML: Print $xml->asXML().

Refactored Code Example

Here is how your main script should look to guarantee a valid XML response:

<?php
// Ensure no whitespace exists between <?php and this line

require_once('connect.php');

// Verify connection status before proceeding
if ($conn->connect_error) {
    // Handle connection errors gracefully, perhaps by logging or returning a specific error code
    exit("Database connection failed"); 
}

$sql = "select * from projet";
$result = $conn->query($sql);

$xml = new SimpleXMLElement('<xml/>');

if ($result && $result->num_rows > 0) {
    while($row = $result->fetch_assoc()) {
        $mydata = $xml->addChild('mydata');
        $mydata->addChild('Id', $row['idProjet']);
    }
} else {
    // Instead of echoing "0 results", add an element to the XML
    // This ensures the response is always valid XML regardless of data
    $xml->addChild('status', 'no_records_found');
}

// Set header BEFORE any output (echo/print)
header("Content-Type: text/xml; charset=UTF-8");

// Flush buffers if necessary, though asXML() usually handles this
echo $xml->asXML();

$conn->close();
?>

Key Technical Details

  • Whitespace Sensitivity: In PHP, <?php echo " "; sends a space. If your file starts with indentation or a newline before the code, that byte is sent immediately. For XML, this breaks the parser expecting <?xml.... Always start your file content right after the opening tag.
  • Header Placement: The header() function must be called before any output. If connect.php has an echo statement, it might trigger output before the main script sets the header. You can force buffering with ob_start() at the very top of your main file if you suspect external scripts are leaking output.
  • Database Connectivity: Your connect.php currently echoes "connected succesfully". In a production environment or when generating API responses, you should remove this echo statement entirely. Logging errors to a file is better than sending debug strings to the browser, which pollutes the response body and breaks strict content types like XML.

Why This Matters for APIs

When building an API endpoint, consistency is key. Clients expect a valid XML document or a clear error code (like HTTP 500). Mixing plain text responses (echo "0 results") with XML responses creates ambiguity. By wrapping all logic in the SimpleXMLElement object and handling the "empty result" case as an XML node, you maintain a strict contract with your consumers.

If you are migrating this application to a framework later, Laravel provides robust methods for returning JSON or XML responses that handle headers automatically, eliminating the risk of accidental output breaking your response format. You can reference https://laravelcompany.com if you are interested in how modern frameworks abstract these low-level output handling details away from you.

By restructuring your script to prioritize header setting and XML generation before any raw echo statements, the "Document is empty" error will resolve itself, and your XML output will be valid for all parsers.

Our network