Trusting Safe Values
Last updated
What is Trusting Safe Values?
Sometimes applications genuinely need to include executable code, display an <iframe> from some URL, or construct potentially dangerous URLs. To prevent automatic sanitization in these situations, tell Angular that you inspected a value, checked how it was created, and made sure it is secure. Do be careful. If you trust a value that might be malicious, you are introducing a security vulnerability into your application. If in doubt, find a professional security reviewer.
Free resources to learn Trusting Safe Values
- Official docsTrusting Safe Values
More in stage 18: Developer Tools
- Developer Tools
- Angular CLI
- DevTools
- Local Setup
- Language Service
- Deployment
- Libraries
- End-to-End Testing
- Using Libraries
- Schematics
- Creating Libraries
- Build Environments
- Cross-site Scripting
- HTTP Vulnerabilities
- CLI Builders
- Sanitization
- Cross-site Request Forgery
- AoT Compilation
- HttpClient CSRF
- Enforce Trusted Types
- XSRF protection
- Cross-site Script Inclusion
- NGXS
- NgRx
- RxJS Interop
- Inputs as Signals
- Queries as Signals
- Model Inputs
Trusting Safe Values: common questions
Can I learn Trusting Safe Values in Hindi?
This lesson is written in English. Once you sign in, open it in the interactive course and ask the AI tutor to explain Trusting Safe Values in Hindi or Hinglish. The tutor answers from this lesson’s own text, so it stays on the syllabus, and it runs on your own Google, OpenAI or Anthropic key.
Is this Trusting Safe Values tutorial for beginners?
It is lesson 112 of 158 in the free Angular roadmap, in stage 18, Developer Tools. If you are new to Angular, start from stage 1 and come back here in order; if you already know the earlier stages, this lesson stands on its own.