On Jul 9, 2012, at 1:44 PM, Phil Pishioneri wrote:

> On 7/9/12 11:17 AM, Andrew Mortensen wrote:
>> Yes, it should only throw on fatal connect errors. What other errors are you 
>> proposing to lump with WSATIMEDOUT?
> [above should be WSAETIMEDOUT]
> 
> Reviewing the list at
> 
> http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx
> 
> I'll nominate (including WSAETIMEDOUT)
> 
> WSAENETDOWN
> WSAENETUNREACH
> WSAETIMEDOUT
> WSAECONNREFUSED
> WSAEHOSTDOWN
> WSAEHOSTUNREACH

Those seem reasonable. An alternative is not to treat *any* connect error as 
fatal. This is what the apache filters do. The failure bubbles up and 
ultimately the filters log an error and return a 503 Service Unavailable error 
to the user agent. This seems like better UX to me, since unprotected pages are 
still available regardless of the problems the filter/module is having.

andrew
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to