* Start catching rogue SocketExceptions which occur (at least on mono) when a response stream for a request which actually required no response, is closed
parent
11f057f90b
commit
70233d937f
|
@ -199,6 +199,16 @@ namespace OpenSim.Framework.Servers
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
catch (System.Net.Sockets.SocketException e)
|
||||||
|
{
|
||||||
|
// At least on linux, it appears that if the client makes a request without requiring the response,
|
||||||
|
// an unconnected socket exception is thrown when we close the response output stream. There's no
|
||||||
|
// obvious way to tell if the client didn't require the response, so instead we'll catch and ignore
|
||||||
|
// the exception instead.
|
||||||
|
//
|
||||||
|
// An alternative may be to turn off all response write exceptions on the HttpListener, but let's go
|
||||||
|
// with the minimum first
|
||||||
|
}
|
||||||
catch (Exception e)
|
catch (Exception e)
|
||||||
{
|
{
|
||||||
m_log.ErrorFormat("[BASE HTTP SERVER]: HandleRequest() threw {0}", e);
|
m_log.ErrorFormat("[BASE HTTP SERVER]: HandleRequest() threw {0}", e);
|
||||||
|
|
Loading…
Reference in New Issue