Switch faq-link and error-link from md to html

Author: cors-errors

_error-messages/a2da.md

@@ -19,7 +19,7 @@ Even if you aren't intentionally using redirects there are two common ways that
 If you're unsure why a redirect is occurring then the first step is to check the `Location` response header. Often the
 new location will only differ from the original location by a single character so you may need to check it very
 carefully. Safari and recent versions of Chrome don't show the preflight request separately in the *Network* tab of the
-developer tools, making it difficult to check the response headers. See {% include faq-link.md faq="b56b" %} for more
+developer tools, making it difficult to check the response headers. See {% include faq-link.html faq="b56b" %} for more
 information.
 
 While the server should not be attempting to redirect the preflight `OPTIONS` request it is usually trivial to fix in
@@ -29,5 +29,5 @@ the client by updating the URL to avoid the redirect altogether.
 
 Related:
 
-* {% include faq-link.md faq="c320" %}
-* {% include faq-link.md faq="b56b" %}
+* {% include faq-link.html faq="c320" %}
+* {% include faq-link.html faq="b56b" %}

_error-messages/a384.md

@@ -20,7 +20,7 @@ This message is intended to provide extra feedback to the developer but ultimate
 `Origin` request header will always be well-formed so if the `Access-Control-Allow-Origin` header can't be parsed it
 can't be a match.
 
-This is very similar to {% include error-link.md message="f6e6" text="another error message" %}. That error relates to
+This is very similar to {% include error-link.html message="f6e6" text="another error message" %}. That error relates to
 the preflight `OPTIONS` request, whereas this error specifically concerns the main request.
 
 If you are making the request using the `fetch` API then you'll also see the following text at the end of the error
@@ -31,5 +31,5 @@ message:
   mode to 'no-cors' to fetch the resource with CORS disabled.
 </blockquote>
 
-For more information about opaque responses see {% include faq-link.md faq="dfdb" %}. Using an opaque response will
+For more information about opaque responses see {% include faq-link.html faq="dfdb" %}. Using an opaque response will
 suppress the error message but it won't allow you to access the response details.

_error-messages/aa0c.md

@@ -13,11 +13,11 @@ The best place to start with debugging this error is to check which status code
 response body that provides further information.
 
 This can be tricky in browsers that don't show the preflight `OPTIONS` request separately in the developer tools. See
-{% include faq-link.md faq="b56b" %} for more information.
+{% include faq-link.html faq="b56b" %} for more information.
 
 The other thing to check is the request URL. Specifically check in the developer tools rather than in your code. Make
 sure the URL really is what you intended. Depending on how the server is configured there are several different status
 codes you might receive if the URL is wrong.
 
 Attempts to redirect to a different URL will typically show a different error message. See
-{% include error-link.md message="a2da" text="Redirect is not allowed for a preflight request" %}.
+{% include error-link.html message="a2da" text="Redirect is not allowed for a preflight request" %}.

_error-messages/aa2f.md

@@ -22,5 +22,5 @@ A value of `*` can also be used as a wildcard in `Access-Control-Allow-Headers`.
 
 Related:
 
-* {% include faq-link.md faq="b7f6" %}
-* {% include faq-link.md faq="b040" %}.
+* {% include faq-link.html faq="b7f6" %}
+* {% include faq-link.html faq="b040" %}.

_error-messages/b435.md

@@ -13,14 +13,14 @@ error:
 
 For requests that use `withCredentials` the server response to the preflight `OPTIONS` request must include the header
 `Access-Control-Allow-Credentials` set to the value `true`. The same header must also be included for the main request,
-though omitting it would trigger {% include error-link.md message="bbd3" text="a different error message" %}.
+though omitting it would trigger {% include error-link.html message="bbd3" text="a different error message" %}.
 
-If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.md faq="b7f6" %}.
+If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.html faq="b7f6" %}.
 
 If the message reports a value of `''` then that usually means the header is missing altogether rather than being
 returned with an explicit empty value.
 
 If the error message indicates that the current value is `'true, true'` then that suggests that the header is being
 returned twice.
 
-See also {% include faq-link.md faq="fcd5" %}.
+See also {% include faq-link.html faq="fcd5" %}.

_error-messages/b78f.md

@@ -6,15 +6,15 @@ message: "Response to preflight request doesn't pass access control check: No 'A
 This error indicates that the preflight `OPTIONS` request failed because the server did not include the response header
 `Access-Control-Allow-Origin`.
 
-This is very similar to {% include error-link.md message="e2a2" text="another error message" %}. That error relates to
+This is very similar to {% include error-link.html message="e2a2" text="another error message" %}. That error relates to
 the main request, whereas this error specifically concerns the preflight `OPTIONS` request.
 
-If you're new to CORS see {% include faq-link.md faq="e9f4" %} for more information.
+If you're new to CORS see {% include faq-link.html faq="e9f4" %} for more information.
 
-If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.md faq="b7f6" %}.
+If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.html faq="b7f6" %}.
 
 If you've attempted to configure the CORS headers but you're still seeing this message then try
-{% include faq-link.md faq="ea74" %}.
+{% include faq-link.html faq="ea74" %}.
 
 If you are making the request using the `fetch` API then you'll also see the following text at the end of the error
 message:
@@ -23,5 +23,5 @@ message:
   If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
 </blockquote>
 
-For more information about opaque responses see {% include faq-link.md faq="dfdb" %}. Using an opaque response will
+For more information about opaque responses see {% include faq-link.html faq="dfdb" %}. Using an opaque response will
 suppress the error message but it won't allow you to access the response details.

_error-messages/bbd3.md

@@ -19,4 +19,4 @@ returned with an explicit empty value.
 If the error message indicates that the current value is `'true, true'` then that suggests that the header is being
 returned twice.
 
-See also {% include faq-link.md faq="fcd5" %}.
+See also {% include faq-link.html faq="fcd5" %}.

_error-messages/d514.md

@@ -4,6 +4,6 @@ message: "Response to preflight request doesn't pass access control check: The '
 ---
 
 This error specifically refers to the preflight `OPTIONS` request but is otherwise identical to
-{% include error-link.md message="f5ab" text="an earlier error message" %}.
+{% include error-link.html message="f5ab" text="an earlier error message" %}.
 
-If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.md faq="b7f6" %}.
+If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.html faq="b7f6" %}.

_error-messages/d897.md

@@ -49,5 +49,5 @@ message:
   mode to 'no-cors' to fetch the resource with CORS disabled.
 </blockquote>
 
-For more information about opaque responses see {% include faq-link.md faq="dfdb" %}. Using an opaque response will
+For more information about opaque responses see {% include faq-link.html faq="dfdb" %}. Using an opaque response will
 suppress the error message but it won't allow you to access the response details.

_error-messages/da36.md

@@ -4,6 +4,6 @@ message: "Response to preflight request doesn't pass access control check: The '
 ---
 
 This error specifically refers to the preflight `OPTIONS` request but is otherwise identical to
-{% include error-link.md message="d897" text="an earlier error message" %}.
+{% include error-link.html message="d897" text="an earlier error message" %}.
 
-If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.md faq="b7f6" %}.
+If you are unclear what a preflight `OPTIONS` request is then see {% include faq-link.html faq="b7f6" %}.