QuestenaПрактика, после которой понятно, что повторить
Вопрос 4

How does RFC 5789 characterize the PATCH method?

  1. Safe when the patch document is empty, otherwise idempotent
  2. Idempotent but not safe, like PUT
  3. Idempotent whenever the patch document is applied atomically
  4. Neither safe nor idempotent, although a particular patch format can be issued in an idempotent wayПравильный ответ

Объяснение

PATCH is defined as neither safe nor idempotent, because a patch document may describe a relative change that compounds when applied twice. The spec adds that a request can be issued so as to be idempotent, and recommends a conditional request with a strong ETag to guard against collisions; atomicity is a separate requirement and does not imply idempotency.

Продолжить работу с тестом

Начать тренировку
Вопрос 4: How does RFC 5789 characterize the PATCH method? · HTTP Semantics · Questena