I have ported an HTTP Server to use the Secure Socket Library. Since the port, I get an occasional exception:
Unable to read data from the transport connection

This occurs *after* successfully reading the first line of the HTTP request from the client, i.e. when reading the first line of the HTTP headers.

I am using a StreamReader created with a SecureNetworkStream as a parameter.

There does not seem to be any pattern to when exceptions occur. It is not related to load or particular types of transactions.

Has anyone seen anything like this or can anyone offer an explanation?

I'd be happy to post code if it will help.

Thanks!
Berl Steiner

I have since recoded using blocking Receives and this seems to have worked. Perhaps it's a bug in the ReadLine implementation...?