[PATCH] 3.2/3.HEAD: send HTTP/1.1 on CONNECT responses

3.2 and later send HTTP/1.1 version on all regular response lines.

CONNECT seems to have been missed somehow. This corrects the omission so
the hard-coded CONNECT reply strings send 1.1 as well.

I'm not certain, but this may explain some of the very rare CONNECT
problems seen in 3.2+.

Alex:
  if its not too much trouble could you add this to the compliance testing
queue to see if it fixes/breaks anything before it gets committed please?

Amos