mirror of
https://github.com/servo/servo.git
synced 2025-10-04 02:29:12 +01:00
88afe38092
Implementation of HTTP Redirect Fetch step I've made a first draft of a complete implementation of HTTP Redirect Fetch, most of which is just refactored out of HTTP Fetch. I've also made some minor changes in a few other steps, all collected in the second commit, based on recent changes to the Fetch Standard. Since HTTP Redirect Fetch is so new, I figured now would be a fine time to make those other changes. The biggest thing on my mind right now is how the spec says[1] "This algorithm will be used by HTML's "navigate" algorithm in addition to HTTP fetch above." This makes me think that this function, as well as HTTP Fetch, need to public, or at least have a public-facing function- since each Fetch function takes an Rc<Request>, which might be weird to require callers to supply. [1] https://fetch.spec.whatwg.org/#http-redirect-fetch <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.svg" height="40" alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/9608) <!-- Reviewable:end --> |
||
|---|---|---|
| .. | ||
| fetch | ||
| about_loader.rs | ||
| Cargo.toml | ||
| cookie.rs | ||
| cookie_storage.rs | ||
| data_loader.rs | ||
| file_loader.rs | ||
| hsts.rs | ||
| http_loader.rs | ||
| image_cache_thread.rs | ||
| lib.rs | ||
| mime_classifier.rs | ||
| pub_domains.rs | ||
| resource_thread.rs | ||
| storage_thread.rs | ||
| websocket_loader.rs | ||
