diff options
author | bors-servo <metajack+bors@gmail.com> | 2015-07-22 10:23:05 -0600 |
---|---|---|
committer | bors-servo <metajack+bors@gmail.com> | 2015-07-22 10:23:05 -0600 |
commit | ab3d6c472d409c1602c873dcdcb495a7fec9d4b0 (patch) | |
tree | 40e1dda4ac333ec4b12193e9a9c2d49ad4d14180 /components/script/dom/node.rs | |
parent | 6b4f1a42f08f66519af310b7c7777d77cc3d0834 (diff) | |
parent | 118122da382622f4c7e8e16174a37e9870f004d9 (diff) | |
download | servo-ab3d6c472d409c1602c873dcdcb495a7fec9d4b0.tar.gz servo-ab3d6c472d409c1602c873dcdcb495a7fec9d4b0.zip |
Auto merge of #6490 - samfoo:hsts-preload, r=jdm
Implement HSTS (preload-only)
Implement HSTS (preload-only) servo/servo#6105
* Downloads the HSTS preload list from the chromium repo (same as gecko), then convert it to a list appropriate for servo.
* Reads the preload list when creating a resource task, and implements STS for those domains.
Still todo:
* Read Strict-Transport-Security headers from servers and add details to the in-memory HSTS list. (note: this requires hyper or servo to implement an STS header struct. Hyper seems like the appropriate location, so I will create an issue/PR there soon). The work for this is nearly done with the exception of adding a new ControlMsg and the new header.
* Persist HSTS list to disk with known hosts (perhaps a different issue should be raised for this?)
<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6490)
<!-- Reviewable:end -->
Diffstat (limited to 'components/script/dom/node.rs')
0 files changed, 0 insertions, 0 deletions