On 7/9/12 2:00 PM, Andrew Mortensen wrote:
> 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.

If you think the logic flow of CosignModule is similar enough to the 
apache filter, I like it. (I was trying to compare the two and getting 
bogged down by other work.)

I know that the one group here who has experienced the bug a couple of 
times would like a version that kept serving unprotected pages.

-Phil

------------------------------------------------------------------------------
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