doc: add docs for synchronous XHR requests

Author: mschile

docs/app/references/error-messages.mdx

@@ -801,10 +801,10 @@ read a unique identifier from your CI provider as described in our
 
 You may encounter this error if Cypress is detecting the exact same CI Build ID
 matching a previous CI Build ID in a run that was completed over 24 hours ago.
-You cannot run tests on a run that has been complete for that long. ​ ​You can
+You cannot run tests on a run that has been complete for that long. You can
 see the CI Build ID that is detected for each completed run by looking at the
 details section at the top of your run in
-[Cypress Cloud](https://on.cypress.io/cloud). ​ ​You can generate and pass in
+[Cypress Cloud](https://on.cypress.io/cloud). You can generate and pass in
 your own unique CI Build ID per run as described
 [here](/app/references/command-line#cypress-run-ci-build-id-lt-id-gt).
 
@@ -946,6 +946,22 @@ there.
 It's possible to enable debugging these scripts by adding the `crossorigin`
 attribute and setting a `CORS` header.
 
+### <Icon name="exclamation-triangle" color="red" /> Synchronous XHR requests
+
+:::caution
+
+<strong>Note</strong>
+
+Synchronous XHR requests often cause hangs on the web, especially with poor network conditions or when the remote server is slow to respond. Synchronous XHR is now deprecated and should be avoided in favor of asynchronous requests.
+
+:::
+
+Cypress does not fully support synchronous XHR requests in the following scenarios:
+
+- When using `cy.intercept()` with a `routeHandler` to intercept a synchronous XHR request.
+- When applying cookies to a synchronous XHR request.
+- When setting cookies from the response of a synchronous XHR request.
+
 ## Browser Errors
 
 {/* keep old hash */}