add callouts for url redirects

khadni · khadni · commit 61b8ab4093b6 · 2025-12-16T10:42:47.000-05:00
diff --git a/reports/llms-report.json b/reports/llms-report.json
@@ -1,30 +1,30 @@
 {
-  "startedAt": "2025-12-15T18:30:25.869Z",
+  "startedAt": "2025-12-16T15:42:34.752Z",
   "siteBase": "https://docs.chain.link",
   "sections": [
     {
       "section": "cre-go",
       "pagesProcessed": 84,
       "outputPath": "src/content/cre/llms-full-go.txt",
-      "bytes": 673266,
+      "bytes": 674210,
       "prevBytes": 673266,
-      "deltaBytes": 0
+      "deltaBytes": 944
     },
     {
       "section": "cre-ts",
       "pagesProcessed": 79,
       "outputPath": "src/content/cre/llms-full-ts.txt",
-      "bytes": 629202,
+      "bytes": 630146,
       "prevBytes": 629202,
-      "deltaBytes": 0
+      "deltaBytes": 944
     },
     {
       "section": "vrf",
       "pagesProcessed": 35,
       "outputPath": "src/content/vrf/llms-full.txt",
       "bytes": 301005,
-      "prevBytes": 301012,
-      "deltaBytes": -7
+      "prevBytes": 301005,
+      "deltaBytes": 0
     },
     {
       "section": "ccip",
@@ -39,8 +39,8 @@
       "pagesProcessed": 37,
       "outputPath": "src/content/data-feeds/llms-full.txt",
       "bytes": 302811,
-      "prevBytes": 302816,
-      "deltaBytes": -5
+      "prevBytes": 302811,
+      "deltaBytes": 0
     },
     {
       "section": "data-streams",
@@ -87,8 +87,8 @@
       "pagesProcessed": 12,
       "outputPath": "src/content/resources/llms-full.txt",
       "bytes": 340405,
-      "prevBytes": 340412,
-      "deltaBytes": -7
+      "prevBytes": 340405,
+      "deltaBytes": 0
     },
     {
       "section": "architecture-overview",
@@ -123,5 +123,5 @@
       "deltaBytes": 0
     }
   ],
-  "finishedAt": "2025-12-15T18:30:30.307Z"
+  "finishedAt": "2025-12-16T15:42:38.996Z"
 }
diff --git a/src/content/cre/llms-full-go.txt b/src/content/cre/llms-full-go.txt
@@ -10764,6 +10764,11 @@ All HTTP requests are wrapped in a consensus mechanism to provide a single, reli
 
 This guide assumes you have a basic understanding of CRE. If you are new, we strongly recommend completing the [Getting Started tutorial](/cre/getting-started/overview) first.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## Choosing your approach
 
 ### Use `http.SendRequest` (Section 1) when:
@@ -10999,6 +11004,11 @@ For this example, we will use <a href="https://webhook.site/" target="_blank">**
 
 This guide assumes you have a basic understanding of CRE. If you are new, we strongly recommend completing the [Getting Started tutorial](/cre/getting-started/overview) first.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## 1. The `http.SendRequest` Pattern (recommended)
 
 The `http.SendRequest` helper function is the simplest and recommended way to make `POST` requests. It automatically handles the `cre.RunInNodeMode` pattern for you.
@@ -11532,6 +11542,11 @@ This guide shows how to send a cryptographically signed report (generated by you
 - Understanding of [generating reports](/cre/guides/workflow/using-evm-client/onchain-write/generating-reports-single-values)
 - A generated report from `runtime.GenerateReport()`
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## Quick start: Minimal example
 
 Here's the simplest possible workflow that generates and submits a report via HTTP:
@@ -13956,6 +13971,11 @@ The HTTP Client lets you make requests to external APIs from your workflow. Each
 
 Defines the parameters for an outgoing HTTP request.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 | Field           | Type                   | Description                                                                                                               |
 | --------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------- |
 | `Url`           | `string`               | The URL of the API endpoint.                                                                                              |
diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt
@@ -9513,6 +9513,11 @@ All HTTP requests are wrapped in a consensus mechanism to provide a single, reli
 
 This guide assumes you have a basic understanding of CRE. If you are new, we strongly recommend completing the [Getting Started tutorial](/cre/getting-started/overview) first.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## Choosing your approach
 
 ### Use `sendRequest` (Section 1) when:
@@ -9896,6 +9901,11 @@ For this example, we will use <a href="https://webhook.site/" target="_blank">**
 
 This guide assumes you have a basic understanding of CRE. If you are new, we strongly recommend completing the [Getting Started tutorial](/cre/getting-started/overview) first.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## 1. The High-Level `sendRequest` Pattern (recommended)
 
 The high-level `sendRequest()` method is the simplest and recommended way to make `POST` requests. It automatically handles the `runInNodeMode` pattern for you.
@@ -10333,6 +10343,11 @@ This guide shows how to send a cryptographically signed report (generated by you
 - Familiarity with [making POST requests](/cre/guides/workflow/using-http-client/post-request)
 - Familiarity with `runtime.report()` (covered [below](#generating-reports-for-http-submission))
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 ## Quick start: Minimal example
 
 Here's the simplest possible workflow that generates and submits a report via HTTP:
@@ -13804,6 +13819,11 @@ const fetchPrice = (sendRequester: HTTPSendRequester, url: string): number => {
 
 Defines the parameters for an outgoing HTTP request.
 
+
+<Aside type="caution" title="Redirects are not supported">
+  HTTP requests to URLs that return redirects (3xx status codes) will fail. Ensure the URL you provide is the final destination and does not redirect to another URL.
+</Aside>
+
 | Field           | Type                                              | Description                                                     |
 | --------------- | ------------------------------------------------- | --------------------------------------------------------------- |
 | `url`           | `string`                                          | The URL of the API endpoint.                                    |
