fe2o3_steel/tests/proxy_hsts.rs
3 operations, oldest first
created by r1870400018:72582, which is this file's identity for as long as the history lasts, whatever it is later renamed to
read the file · who wrote it · compare two states
An operation carries no clock of its own. Each row is therefore dated by the first mark written after it by the same replica, which is one copy of the repository, and that mark is where the command that wrote the operation ended.
+ signed and verified, ? signed by a key this forge does not carry, - unsigned
| Operation | Author | What | When | |
|---|---|---|---|---|
| + | r1870400018:72582 | replica 1870400018 | created fe2o3_steel/tests/proxy_hsts.rs | 40 days ago under "fe2o3_steel: a proxied response to an HTTPS visitor carries the front's HSTS, once -- TLS ends at the front, so the front is where Strict-Transport-Security belongs; handle_proxy_http relayed the upstream's head verbatim and returned before the HSTS fill, so no Zoapedia response carried one (live pre-check probe 7). ServerContext::hsts_value(plain) is the one value both paths use (none over plain HTTP, none at hsts_max_age_secs 0); fe2o3_net::http::fwd::fill_head_field adds a field to a relayed raw head only where it has none of that name (head_has_field, case-insensitive, start line excluded), so an upstream's own policy is relayed as sent and never doubled. tests/proxy_hsts.rs: HTTPS + upstream without HSTS gives exactly the front's; upstream with its own keeps exactly that one; plain loopback visitor gets none. RED on 8a438f0c: no HSTS on the proxied reply; GREEN 1/1, response_headers 4/4, route_dispatch 1/1, fwd unit 8/8." |
| + | r1870400018:72583 | replica 1870400018 | inserted 10.1 KiB | 40 days ago under "fe2o3_steel: a proxied response to an HTTPS visitor carries the front's HSTS, once -- TLS ends at the front, so the front is where Strict-Transport-Security belongs; handle_proxy_http relayed the upstream's head verbatim and returned before the HSTS fill, so no Zoapedia response carried one (live pre-check probe 7). ServerContext::hsts_value(plain) is the one value both paths use (none over plain HTTP, none at hsts_max_age_secs 0); fe2o3_net::http::fwd::fill_head_field adds a field to a relayed raw head only where it has none of that name (head_has_field, case-insensitive, start line excluded), so an upstream's own policy is relayed as sent and never doubled. tests/proxy_hsts.rs: HTTPS + upstream without HSTS gives exactly the front's; upstream with its own keeps exactly that one; plain loopback visitor gets none. RED on 8a438f0c: no HSTS on the proxied reply; GREEN 1/1, response_headers 4/4, route_dispatch 1/1, fwd unit 8/8." |
| + | r1870400018:76797 | replica 1870400018 | inserted 36 bytes | 14 days ago under a mark the tool wrote |