Merge pull request json-api#1589 from timothystone/gh-pages

dgeb · web-flow · commit d9f3a52e1ea3 · 2021-10-18T09:15:08.000-04:00
Remove redirect in link to PATCH RFC
diff --git a/faq/index.md b/faq/index.md
@@ -62,15 +62,15 @@ non-standard actions they support. Feel free to
 
 Using PUT to partially update a resource (i.e. to change only some of its state)
 is not allowed by the
-[HTTP specification](https://tools.ietf.org/html/rfc7231#section-4.3.4).
+[HTTP specification](https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.4).
 Instead, PUT is supposed to completely replace the state of a resource:
 
 > “The PUT method requests that the state of the target resource be **created
   or replaced** with the state…in the request message payload. A successful PUT
   of a given representation would suggest that a subsequent GET on that same
   target resource will result in an equivalent representation being sent…”
 
-The correct method for partial updates, therefore, is [PATCH](http://tools.ietf.org/html/rfc5789),
+The correct method for partial updates, therefore, is [PATCH](https://datatracker.ietf.org/doc/html/rfc5789),
 which is what JSON:API uses. And because PATCH can also be used compliantly for
 full resource replacement, JSON:API hasn't needed to define any behavior for
 PUT so far. However, it may define PUT semantics in the future.
