Kaushal Jha, ZEDO wrote:
thats becoz the server above it sent a
"HTTP/1.1 200" instead of "HTTP/1.1 200 OK"
the after the status number 200 apache was expecting an "OK" :)
Not strictly true - the spec says the line must read "HTTP/<major>.<minor> XXX <response string>", and the response string can be "". The thing is the space after the XXX and before the possibly empty result string must be there.
Apparently the space is there though according to the original post, so it could be a problem with the way Apache handles empty result strings.
Regards, Graham --
