tis 2016-08-09 klockan 11:47 -0600 skrev Alex Rousskov: > > Yep, that matches both my understanding and motivation to return ERR > in > the explicitly configured on-persistent-overload=err case.
I'd say make it configurable. on-persistent-overload=abort/err/ok/unknown to represent all three possible states. But that is based on the assumption that unknown is "outcome is not known" and that Squid then skips the access rule and looks at next rule. Have not looked in detail in how current Squid operated with these conditions. Starting with only abort/err is good. err should then map to the same as a negative helper response which is the most clear buldingblock to work with then bulding access lists. It does not make sense that err in this context should map to different logics depending on the directive. Regards Henrik _______________________________________________ squid-dev mailing list squid-dev@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-dev
