There are situations where the Date header is in another timezone (seems to often be GMT). The date in the local TZ might appear in another header, but not necessarily be easily parsable. Since Pharo's TZ implementation is broken (i.e. it can't convert from GMT to a local historical offset due to DST), allow a cacheable timestamp which can be set manually when needed.
There are situations where the Date header is in another timezone (seems to often be GMT). The date in the local TZ might appear in another header, but not necessarily be easily parsable. Since Pharo's TZ implementation is broken (i.e. it can't convert from GMT to a local historical offset due to DST), allow a cacheable timestamp which can be set manually when needed.