Http 408 Apache

by



I must have had some reason for wanting to do this, although I can’t think of why right now. curl is an excellent tool for ad hoc HTTP requests.

Http code 408 apache

On a server running Apache 2.4.6, first I tried:

# nc 127.0.0.1 80
GET / HTTP/1.1

If you have recently updated the WordPress just before the 408 Request Timeout appeared, you may need to rollback to the previous version. Similarly, any extension, any modules or even any plugin or theme that you may have recently upgraded can also cause server-side issues, so retrieving to the previous version of those may also help. 57 APACHE HTTP STATUS RESPONSE CODES. Once I compiled the list of Apache recognized HTTP Status Codes, I was dying to see them all in action (i.e. The corresponding ErrorDocument). At first I thought I would have to create a php or perl script emulating each of the 57 HTTP Status Codes, a tedious undertaking I wasn't about to do. The HTTP error code 408 – like all members of the 4xx error series – is one of the messages that indicate a client-side problem. HTTP transport safety. It is important to understand that the HTTP protocol is not well suited for all types of applications. HTTP is a simple request/response oriented protocol which was initially designed to support static or dynamically generated content retrieval. It has never been intended to support transactional operations. HTTP access authentication is explained in 'HTTP Authentication: Basic and Digest Access Authentication'. 10.4.9 408 Request Timeout. The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time. 10.4.10 409 Conflict.

Which returned a HTTP/1.1 400 Bad Request error.

Next I tried:

# printf 'GET /index.html HTTP/1.1rnrn' | nc 127.0.0.1 80

Http 408 Apache

Which also returned a HTTP/1.1 400 Bad Request error.

I decided to take a look at what curl was sending, since that was working:

# curl -v http://127.0.0.1
* About to connect() to 127.0.0.1 port 80 (#0)
* Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 127.0.0.1
> Accept: */*
...

I put the same headers (with a modified User-Agent) into my printf statement:

# printf 'GET /index.html HTTP/1.1rnUser-Agent: nc/0.0.1rnHost: 127.0.0.1rnAccept: */*rnrn' | nc 127.0.0.1 80
HTTP/1.1 200 OK
Date: Sun, 28 Jan 2018 23:11:04 GMT
Server: Apache/2.4.6 (CentOS) PHP/5.4.16
Last-Modified: Sun, 28 Jan 2018 20:10:37 GMT
ETag: '78-563dbb912bfe0'
Accept-Ranges: bytes
Content-Length: 120
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html>
<html>
<head>
<title>well that worked</title>
</head>
<body>
<h1>apache is running</h1>
</body>
</html>

Http

That worked!

I eliminated the User-Agent the Accept headers and it still worked, so the missing Host header was the cause of my problems. I swear I’ve done this before without a Host header though.

I looked up the HTTP specification, and as described in section 5.2 of the RFC:

1. If Request-URI is an absoluteURI, the host is part of the Request-URI. Any Host header field value in the request MUST be ignored.

2. If the Request-URI is not an absoluteURI, and the request includes a Host header field, the host is determined by the Host header field value.

3. If the host as determined by rule 1 or 2 is not a valid host on the server, the response MUST be a 400 (Bad Request) error message.

Recipients of an HTTP/1.0 request that lacks a Host header field MAY attempt to use heuristics (e.g., examination of the URI path for something unique to a particular host) in order to determine what exact resource is being requested.

I could not get it to work with an absoluteURI, even using the example in the RFC. However I did find that I could ignore the Host header if I specified HTTP/1.0:

# printf 'GET / HTTP/1.0rnrn' | nc 127.0.0.1 80

Http 408 Apache 2.4

I also found that Apache didn’t care what the Host header was when using HTTP/1.1, just so long as something was there:

# printf 'GET / HTTP/1.1rnHost: zrnrn' | nc 127.0.0.1 80

Http Error 408 Apache

That’s a little odd. I did not specify a ServerName in my Apache config, but even after I specified ServerName 127.0.0.1:80 in /etc/httpd/conf/httpd.conf and restarted Apache, it still required the Host header and it still didn’t care what the content of the Host header was (so long as it was not empty).