| commit | b5fcd0499a75a0cce309ed93d3c601c0c7ba024e | [log] [tgz] |
|---|---|---|
| author | Frank Piva <[email protected]> | Tue Jun 04 05:08:03 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Jun 04 05:08:03 2024 +0000 |
| tree | 7fb6a4c59d42a9167504337be36845ca17e0d21b | |
| parent | 469950f5d1ed2fa9ae7140cfe38c408ceca602f9 [diff] | |
| parent | 279bb16e3d3b136717b78dbb3afbe8c6aa7d6081 [diff] |
Merge remote-tracking branch 'origin/upstream' am: ea8079c257 am: 279bb16e3d Original change: undetermined Change-Id: I643624349f4dfec306f71b30b966e185fa8b7598 Signed-off-by: Automerger Merge Worker <[email protected]>
Multiple HTTP header fields store timestamps. For example a response created on May 15, 2015 may contain the header Date: Fri, 15 May 2015 15:34:21 GMT. Since the timestamp does not contain any timezone or leap second information it is equvivalent to writing 1431696861 Unix time. Rust’s SystemTime is used to store these timestamps.
This crate provides two public functions:
parse_http_date to parse a HTTP datetime string to a system timefmt_http_date to format a system time to a IMF-fixdateIn addition it exposes the HttpDate type that can be used to parse and format timestamps. Convert a sytem time to HttpDate and vice versa. The HttpDate (8 bytes) is smaller than SystemTime (16 bytes) and using the display impl avoids a temporary allocation.
Read the blog post to learn more.
Fuzz it by installing cargo-fuzz and running cargo fuzz run fuzz_target_1.