Re: MSN Broken Pipe error?
Mark Rowe <[email protected]> Wed, 9 Feb 2005 10:03:19 +1300
| Newsgroups | gmane.network.fire.general |
|---|---|
| Message-ID | <[email protected]> |
On Feb 9, 2005, at 9:12 AM, Sean Corfield wrote: > Has MSN changed its protocol to keep Fire out? Or is MSN just down? A quick glance at <http://messenger.msn.com/> will reveal how "down" MSN Messenger is at the moment. The situation was the same approximately 24 hours ago, and stayed that way for about 6 hours. Last night (New Zealand time -- eg, 12 hours ago) the service was back to normal. > I get Broken Pipe, Disconnected every time I try to connect for the > last day or so... It's probably worth improving the error message that is displayed in this situation. "Broken Pipe" is incredibly non-obvious, and doesn't provide any hint as to what went wrong. It could be worthwhile for the error message to refer the user to <http://messenger.msn.com/Status.aspx> when a connection-related error occurs -- both network-level like "Broken Pipe" and protocol-level like "500 Internal server error", "601 Server is unavailable". Regards, Mark Rowe <http://bdash.net.nz/>
smime.p7s
(application/pkcs7-signature, 3.9 KB) - not displayed