Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm working with our network team to configure layer 7 healthchecking for a WAS 6.1 system.

We're proving the connection in a similar manner to how the device will check it, by opening a telnet on the correct IP and port and then issuing a GET request e.g.

GET /path/index.html

When used with IIS the server handles this and responds with a 200

When used with the WAS 6.1 system, the server responds with a 505 unknown protocol.

If I add the HTTP version to the request it completes correctly e.g.

GET /path/index.html HTTP/1.1

however this seems to cause other problems for the network team so I'm trying to understand why WAS responds in this manner compared with other web-servers

share|improve this question
up vote 2 down vote accepted

Technically, the HTTP version is not optional with HTTP 1.0/1.1. IIS responds to requests without it for HTTP 0.9 compatibility. Some servers are more picky.

RFC2068 - Specifically:

Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.