json-api · ethanresnick · Dec 4, 2018 · Dec 3, 2018
diff --git a/_config.yml b/_config.yml
@@ -50,6 +50,8 @@ port: 9876
 collections:
   format:
     output: true
+  errors:
+    output: true
   profiles:
     output: true
     permalink: /:collection/:path
@@ -66,7 +68,14 @@ defaults:
       path: ""
       type: "profiles"
     values:
-      layout: profile_error
+      layout: error
+      is_spec_page: false
+      show_sidebar: false
+  - scope:
+      path: ""
+      type: "errors"
+    values:
+      layout: error
       is_spec_page: false
       show_sidebar: false
   - scope:

diff --git a/_errors/profile-not-supported.md b/_errors/profile-not-supported.md
@@ -0,0 +1,3 @@
+---
+redirect_to: /format/1.1/#profile-query-parameter
+---
diff --git a/_format/1.1/index.md b/_format/1.1/index.md
@@ -1970,7 +1970,13 @@ query parameter **MUST** equal a URI-encoded whitespace-separated list of profil
 
 If a server receives a request requiring the application of a profile or
 combination of profiles that it can not apply, it **MUST** respond with a `400
-Bad Request` status code.
+Bad Request` status code. The response **MUST** contain an [error object] that
+identifies the `profile` query parameter as the `source` and has the following
+URI as (one of) its `type`s:
+
+```
+https://jsonapi.org/errors/profile-not-supported
+```
 
 > Note: When a client lists a profile in the `Accept` header, it's asking the
 > server to compute its response as normal, but then send the response document

diff --git a/_layouts/profile_error.html → _layouts/error.html b/_layouts/profile_error.html → _layouts/error.html