What is antiforgery for JSON APIs?
PICTURE THIS: A SENTENCE BECOMES TOKENS
The model does not read letters like humans. It reads these pieces, then predicts the next one.
Simple meaning
Browser cookie sessions need antiforgery on state-changing calls.
WHY — ASP.NET instead of guessing?
Why interviewers care about ASP.NET:
who only read docs from people who shipped.
and tied to .NET work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens with tokens?
Before the model can read a sentence, it goes through these steps:
- 1Browser cookie sessions need
antiforgery on state-changing calls.
- 2Bearer token APIs typically
skip cookie CSRF.
- 3Embeddings
I match the auth mode.
- 4Context mix
Attention looks at nearby tokens together.
- 5Next token
The model scores what should come next.
- 6Decode
IDs turn back into readable text.
EXAMPLE — See it in action
Let's see how a real sentence is tokenized (tokens may vary by model):
Note: Actual tokens and IDs depend on the tokenizer (e.g., GPT, Llama, etc.).
Key takeaway
Browser cookie sessions need antiforgery on state-changing calls. Bearer token APIs typically skip cookie CSRF.