Partage de ressources cross-origin

Outcome: Complete the task with Partage de ressources cross-origin (CORS). User context: Un tableau de bord sur app.example.com appelle api.example.net. L'API vérifie la pré-vérification avant les écritures authentifiées et n'autorise que l'origine de production. Technical concept or control: Partage de ressources cross-origin (CORS). Why it fits: Configurez CORS sur le serveur ou la passerelle lorsque le code du navigateur doit lire une autre origine. Do not use it when: N'utilisez pas d'origines génériques avec des identifiants ou ne reflétez pas d'origines inconnues. CORS ne remplace pas l'authentification ou la protection CSRF. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): La norme couvre uniquement le champ d'application énuméré. Elle ne choisit ni le style visuel, ni la décision de produit, ni l'exemple de Vibulary. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.