Report what was applied
02Preference-Applied is an optional response field listing preferences the server honored. It does not repeat preference parameters.
The same behavior may occur without Preference-Applied. Do not conclude ignored merely from its absence, or assume a representation-shaped body always proves the preference was applied.
Source for this drawing: RFC 7240 · Read RFC section 3 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
Preference-Applied MAY appear; it is useful when the response alone would be ambiguous.
- Preference-Applied MAY appear; it is useful when the response alone would be ambiguous.
- Its syntax includes preference names and optional values, without the semicolon parameters allowed in Prefer.
- Absence of this optional field is not proof a preference was ignored. Observe the actual response and the application contract.
Examples show one chosen server policy. Preferences are optional; consult the linked requirements, errata and RFC 8144 WebDAV update.
Read the RFC section ↗