> At first glance, I think there's an even more fundamental problem: > the code in ap_cache_check_freshness() appears to be mixing times > measured in microseconds (the result of ap_cache_current_age()) > with times measured in seconds (everything that it gets from the > HTTP header).
And does that surprise you? Probably not. Add one more to the continuing saga of errors due to flagrant type name abuse. ....Roy
