зеркало из https://github.com/mozilla/gecko-dev.git
2650d582c6
The current logic for a cors cache match does not consider "credentials is false and request's credentials mode is not "include" or credentials is true." I could have missed something, but `CacheRequestDetails::credentials` is set to true if credentials mode is "include", and false otherwise. So `(!cors_cache.credentials && !cors_req.credentials) || cors_cache.credentials` would be directly following the spec, but unless I'm mistaken `cors_cache.credentials || !cors_req.credentials` is logically the same. Fixes: #10525 Source-Repo: https://github.com/servo/servo Source-Revision: 3d38a60cee8a2e19ae8f04df7c2374fc9d97999c |
||
|---|---|---|
| .. | ||
| image | ||
| Cargo.toml | ||
| hosts.rs | ||
| image_cache_thread.rs | ||
| lib.rs | ||
| net_error_list.rs | ||
| request.rs | ||
| response.rs | ||
| storage_thread.rs | ||