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

Author: cors-errors

Diff for: _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" %}

Diff for: _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.

Diff for: _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" %}.

Diff for: _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" %}.

Diff for: _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" %}.

Diff for: _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.

Diff for: _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" %}.

Diff for: _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" %}.

Diff for: _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.

Diff for: _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" %}.

Diff for: _error-messages/dab3.md

@@ -14,13 +14,13 @@ This error indicates that the `Access-Control-Allow-Origin` response header had
 not allowed for requests that use `withCredentials`.
 
 In many cases `withCredentials` isn't required and can simply be removed. If you aren't using cookies then you probably
-don't need it. For more information see {% include faq-link.md faq="fcd5" %}.
+don't need it. For more information see {% include faq-link.html faq="fcd5" %}.
 
 If you do need `withCredentials` then you'll have to change the server so that it doesn't return `*` for
 `Access-Control-Allow-Origin`. Instead the server should check that the `Origin` request header contains an allowed
 origin before echoing that origin value back in `Access-Control-Allow-Origin`.
 
-If you want to understand why this restriction on using `*` exists then see {% include faq-link.md faq="ffcc" %}. By
+If you want to understand why this restriction on using `*` exists then see {% include faq-link.html faq="ffcc" %}. By
 extension it's important that the server does not simply echo back all origins: only trusted origins should be allowed.
 
 There are browser extensions that automatically set the `Access-Control-Allow-Origin` header to `*`, overriding any

Diff for: _error-messages/e048.md

@@ -20,4 +20,4 @@ headers. In that case the browser will still include the `Access-Control-Request
 A value of `*` can also be used as a wildcard in `Access-Control-Allow-Methods`. However, this is not allowed when using
 `withCredentials` and will result in the same 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" %}.

Diff for: _error-messages/e2a2.md

@@ -4,13 +4,13 @@ message: No 'Access-Control-Allow-Origin' header is present on the requested res
 
 This error indicates that the server response did not include the header `Access-Control-Allow-Origin`.
 
-This is very similar to {% include error-link.md message="b78f" text="another error message" %}. That error relates to
+This is very similar to {% include error-link.html message="b78f" text="another error message" %}. That error relates to
 the preflight `OPTIONS` request, whereas this error specifically concerns the main 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'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:
@@ -19,5 +19,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.

Diff for: _error-messages/efd0.md

@@ -12,6 +12,6 @@ error:
 </blockquote>
 
 This error specifically refers to the preflight `OPTIONS` request but is otherwise identical to
-{% include error-link.md message="dab3" text="an earlier error message" %}.
+{% include error-link.html message="dab3" 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" %}.

Diff for: _error-messages/f5ab.md

@@ -14,5 +14,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.

Diff for: _error-messages/f6e6.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="a384" text="an earlier error message" %}.
+{% include error-link.html message="a384" 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" %}.

Diff for: _faq/a313.md

@@ -4,4 +4,4 @@ question: Why am I seeing an OPTIONS request instead of the GET/POST/etc. reques
 
 That is the *preflight request*.
 
-See {% include faq-link.md faq="b7f6" %} for more information.
+See {% include faq-link.html faq="b7f6" %} for more information.

Diff for: _faq/a8d2.md

@@ -18,18 +18,18 @@ If you're seeing a CORS-related error message but you aren't sure what it means
 The next thing to try is the *Network* tab of the developer tools. Find the request that isn't working and
 check exactly what is being sent each way.
 
-If you're seeing an `OPTIONS` request that you weren't expecting then see {% include faq-link.md faq="a313" %}.
+If you're seeing an `OPTIONS` request that you weren't expecting then see {% include faq-link.html faq="a313" %}.
 
-If you're seeing the warning *'Provisional headers are shown'* then see {% include faq-link.md faq="b56b" %}.
+If you're seeing the warning *'Provisional headers are shown'* then see {% include faq-link.html faq="b56b" %}.
 
 If you think all the headers look correct then you can check them using our [CORS header checker](/header-checker).
 
 ---
 
 Related:
 
-* {% include faq-link.md faq="ea74" %}
-* {% include faq-link.md faq="cdc8" %}
-* {% include faq-link.md faq="b1b0" %}
-* {% include faq-link.md faq="a313" %}
-* {% include faq-link.md faq="b56b" %}.
+* {% include faq-link.html faq="ea74" %}
+* {% include faq-link.html faq="cdc8" %}
+* {% include faq-link.html faq="b1b0" %}
+* {% include faq-link.html faq="a313" %}
+* {% include faq-link.html faq="b56b" %}.

Diff for: _faq/abe3.md

@@ -13,6 +13,6 @@ to be part of the *origin* when the browser decides whether or not to use CORS.
 
 Related:
 
-* {% include faq-link.md faq="d1a6" %}
-* {% include faq-link.md faq="b667" %}
-* {% include faq-link.md faq="f173" %}
+* {% include faq-link.html faq="d1a6" %}
+* {% include faq-link.html faq="b667" %}
+* {% include faq-link.html faq="f173" %}

Diff for: _faq/b040.md

@@ -7,7 +7,7 @@ The headers `Access-Control-Request-Method` and `Access-Control-Request-Headers`
 preflight in required.
 
 This can be tricky as recent versions of Chrome don't show the preflight request in the developer tools. See
-{% include faq-link.md faq="b56b" %} for more information.
+{% include faq-link.html faq="b56b" %} for more information.
 
 First check `Access-Control-Request-Method`. If it's set to `GET`, `HEAD` or `POST` then that isn't the problem. Those 3
 request methods are considered safe and won't trigger a preflight request. For any other values, e.g. `PUT` or `DELETE`,
@@ -37,5 +37,5 @@ breakpoint just before your request and step into the library code to see exactl
 
 Related:
 
-* {% include faq-link.md faq="b56b" %}
-* {% include faq-link.md faq="b7f6" %}
+* {% include faq-link.html faq="b56b" %}
+* {% include faq-link.html faq="b7f6" %}

Diff for: _faq/b1b0.md

@@ -24,4 +24,4 @@ for more information.
 
 Related:
 
-* {% include faq-link.md faq="b56b" %}
+* {% include faq-link.html faq="b56b" %}

Diff for: _faq/b4d0.md

@@ -15,7 +15,7 @@ One particularly noteworthy error shown in Chrome is:
 Interestingly, the same problem in Firefox doesn't show any error message, the request just fails without explanation.
 
 The source of this problem is that the URI is missing the prefix `http://` or `https://`, so the browser interprets the
-`localhost:` as being the *scheme* of the URI. {% include error-link.md message="c0d3" text="More information" %}.
+`localhost:` as being the *scheme* of the URI. {% include error-link.html message="c0d3" text="More information" %}.
 
 However, assuming you aren't seeing that particular error...
 
@@ -24,7 +24,7 @@ In most browsers the developer tools must be open before you make the request, o
 Check you don't have any filters turned on which could be hiding your request.
 
 In Safari and recent versions of Chrome you won't be able to see the preflight `OPTIONS` request as a separate request.
-See {% include faq-link.md faq="b56b" %} for more information.
+See {% include faq-link.html faq="b56b" %} for more information.
 
 Preflight `OPTIONS` requests can also be cached, so it's possible you may not see the request you're expecting because a
 cached response has been used instead. If you have access to the server logs you may be able to confirm what requests
@@ -37,4 +37,4 @@ caching problems that might be interfering with your requests.
 
 Related:
 
-* {% include faq-link.md faq="b56b" %}
+* {% include faq-link.html faq="b56b" %}

Diff for: _faq/b56b.md

@@ -38,5 +38,5 @@ Hopefully Chrome will fix the developer tools soon so that this is no longer a p
 
 Related:
 
-* {% include faq-link.md faq="b4d0" %}
-* {% include faq-link.md faq="b1b0" %}
+* {% include faq-link.html faq="b4d0" %}
+* {% include faq-link.html faq="b1b0" %}

Diff for: _faq/b667.md

@@ -28,4 +28,4 @@ In JavaScript you can access the current page's origin using `location.origin`.
 
 Related:
 
-* {% include faq-link.md faq="fe2a" %}
+* {% include faq-link.html faq="fe2a" %}

Diff for: _faq/b6b0.md

@@ -9,7 +9,7 @@ To make the copied request useful you will also need to add the `-I` option. Thi
 output.
 
 In theory you can do the same thing in Chrome but recent versions have made it more difficult to access the `OPTIONS`
-request in the developer tools. See {% include faq-link.md faq="b56b" %} for more information.
+request in the developer tools. See {% include faq-link.html faq="b56b" %} for more information.
 
 Most of the request headers included by a browser aren't necessary from a CORS perspective. Servers will usually ignore
 those other headers when responding to a preflight request. Generally a much simpler cURL request will suffice:
@@ -40,7 +40,7 @@ Breaking this down:
 
 Related:
 
-* {% include faq-link.md faq="b7f6" %}
-* {% include faq-link.md faq="d1a6" %}
-* {% include faq-link.md faq="c7f6" %}
-* {% include faq-link.md faq="b56b" %}
+* {% include faq-link.html faq="b7f6" %}
+* {% include faq-link.html faq="d1a6" %}
+* {% include faq-link.html faq="c7f6" %}
+* {% include faq-link.html faq="b56b" %}