mirror of
https://github.com/servo/servo.git
synced 2025-08-10 07:55:33 +01:00
ff02fdad6d
This change refactors how we notify DevTools about network activity so that all fetches (even those served from cache) appear correctly in the Network panel, and so that DevTools sees request metadata as soon as possible rather than waiting until the end of a full HTTP cycle. - Before, we only send DevTools events inside http_network_fetch, so cached responses (which skip that path) never show up. By emitting a minimal HttpRequest event at the very start of main_fetch (with URL, method, pipeline and browsing IDs), we guarantee every fetch shows up immediately. - Then, by moving HttpResponse notifications out of http_network_fetch into main_fetch (right after process_response and process_response_eof), we ensure DevTools gets status, header, and completion events for both network and cache hits. Leveraging nullable fields in NetworkEventActor lets us incrementally fill in timing, header, and body data later, improving DevTools’ visibility. Testing: Ran servo with `--devtools=6080` flag, cached responses now appear in the network panel Fixes: https://github.com/servo/servo/issues/37869 --------- Signed-off-by: Uthman Yahaya Baba <uthmanyahayababa@gmail.com> |
||
|---|---|---|
| .. | ||
| fetch | ||
| tests | ||
| blob_url_store.rs | ||
| Cargo.toml | ||
| filemanager_thread.rs | ||
| http_status.rs | ||
| image_cache.rs | ||
| indexeddb_thread.rs | ||
| lib.rs | ||
| mime_classifier.rs | ||
| policy_container.rs | ||
| pub_domains.rs | ||
| quality.rs | ||
| request.rs | ||
| response.rs | ||
| storage_thread.rs | ||