Problem with maxAge parameter

[ale5000-git]

If I set maxAge=3600 then it set Cache-Control header correctly but it doesn't set Expires header accordingly that make it useless (instead it is set to a past date, by some seconds).

Responding with a past date in the Expired header (earlier than the Date header value) makes no sense and would be a sign of some serious misconfiguration. That being said, clients would treat such response as "already expired" and not cache it. Same applies if Expires date is equal to Date header value (which is the correct way of server marking the response as "already expired") or having an invalid format.