In which case Apache Httpd writes “X” when connection is closed? Is it client side or server side?

Posted on

In which case Apache Httpd writes “X” when connection is closed? Is it client side or server side? – Problems with loading a website are often blamed on the Internet connection, but even the most perfectly set up network cannot help if there is no service to reply at your destination. One of the most popular HTTP servers used for this task is Apache2. Much of Apache’s popularity can be attributed to its easy installation and use, but never the less it is possible to run into problems with even the easiest of the software. If you’ve encountered an issue loading your web page, follow these simple troubleshooting methods outlined in this guide to attempt to get your web server back up and working again. Below are some tips in manage your apache2 server when you find problem about apache-2.2, httpd, connection, , .

Standing to official Apache mod_log_config docs
I see it writes “X” when “Connection aborted before the response completed”.

    Connection status when response is completed:
    X = Connection aborted before the response completed.
    + = Connection may be kept alive after the response is sent.
    - = Connection will be closed after the response is sent.

What does this mean?
Is there a way I can simulate this behaviour?

Thank you

I see this often.

It may happen when for example Apache is processing the reply and client aborts the connection before the reply has been sent.

Where I see it very often is when I have balancers on top my Apache HTTPD servers, client has made a POST, backend server is taking a while to reply, timeout for F5/Firewall kicks in, connection is silently dropped, when Apache HTTPD has the answer and it is trying to send it back, there is nobody there.

Leave a Reply

Your email address will not be published.