Repository navigation
[TEST UNIQUEMENT · NE PAS FUSIONNER] Protéger le shell SW contre /recovery et les documents secondaires - #24
Draft
iPoower wants to merge 4 commits into
Conversation
… worker [TEST ONLY]
…origin boundaries
…oning [TEST ONLY]
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objectif
Reproduire puis corriger, dans une branche TEST isolée, le risque de remplacement du cache
./index.htmlpar une navigation secondaire HTML. Le Service Worker de Control Vault traite actuellement toute navigation GET de la même origine comme une navigation shell, contrairement à Race Control TEST corrigé dans #245.Méthode
public/sw.js(VM) :/recovery,/recovery.html,drive-config.json,fixture-manifest.jsonne doivent pas être interceptés.Sécurité
Pas de main, de fusion, de production applicative ni de déploiement. PR brouillon, base TEST
test/fortress-drive-execution-20261026(#23). Aucun accès Google, aucune donnée réelle, aucune permission modifiée. Le déploiement TEST actuel reste inchangé et ne doit pas être considéré corrigé avant publication et contrôle indépendant.