[Mono-list] keep-alive connections not working in mono 3/ubuntu

[Chris Ochs]

Thought I'd run this by the list before submitting a bug.  Client is
sending keep-alive headers but actually creating a new tcp connection for
each request.  This was mono built from the 3.2.3 tag, master does the same
thing.  Am I missing something obvious here?

Test code is here:
https://gist.github.com/chrisochs/7113668


Ngrep session showing 2 requests, both with a different origination port by
the client:

T 2013/10/22 23:43:32.686548 127.0.0.1:38695 -> 127.0.0.1:80 [AP]
GET /doc/index.html HTTP/1.1.
Connection: keep-alive.
Host: 127.0.0.1.
.


T 2013/10/22 23:43:32.686611 127.0.0.1:80 -> 127.0.0.1:38695 [AP]
HTTP/1.1 200 OK.
Server: nginx/1.4.1 (Ubuntu).
Date: Wed, 23 Oct 2013 06:43:32 GMT.
Content-Type: text/html.
Content-Length: 0.
Last-Modified: Wed, 23 Oct 2013 06:38:07 GMT.
Connection: keep-alive.
ETag: "52676ecf-0".
Accept-Ranges: bytes.
.


T 2013/10/22 23:43:32.687104 127.0.0.1:38696 -> 127.0.0.1:80 [AP]
GET /doc/index.html HTTP/1.1.
Connection: keep-alive.
Host: 127.0.0.1.
.


T 2013/10/22 23:43:32.687166 127.0.0.1:80 -> 127.0.0.1:38696 [AP]
HTTP/1.1 200 OK.
Server: nginx/1.4.1 (Ubuntu).
Date: Wed, 23 Oct 2013 06:43:32 GMT.
Content-Type: text/html.
Content-Length: 0.
Last-Modified: Wed, 23 Oct 2013 06:38:07 GMT.
Connection: keep-alive.
ETag: "52676ecf-0".
Accept-Ranges: bytes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20131022/51ad67a2/attachment.html>