Skip to content

Commit fca997e

Browse files
issyl0subatoiCopilot
authored
Lowercase example REST API JSONP response header keys (#61789)
Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
1 parent 20376a4 commit fca997e

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

content/rest/using-the-rest-api/using-cors-and-jsonp-to-make-cross-origin-requests.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ $ curl {% data variables.product.rest_url %}?callback=foo
5454
> "x-ratelimit-limit": "5000",
5555
> "x-ratelimit-remaining": "4966",
5656
> "x-ratelimit-reset": "1372700873",
57-
> "Link": [ // pagination headers and other links
57+
> "link": [ // pagination headers and other links
5858
> ["{% data variables.product.rest_url %}?page=2", {"rel": "next"}]
5959
> ]
6060
> },
@@ -90,19 +90,19 @@ document.getElementsByTagName('head')[0].appendChild(script);
9090
</html>
9191
```
9292

93-
All of the headers have the same string value as the HTTP Headers, except `Link`. `Link` headers are pre-parsed for you and come through as an array of `[url, options]` tuples.
93+
All of the headers have the same string value as the HTTP headers, except `link`. The `link` header is pre-parsed for you and comes through as an array of `[url, options]` tuples.
9494

9595
For example, a link that looks like this:
9696

9797
```shell
98-
Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
98+
link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
9999
```
100100

101101
will look like this in the Callback output:
102102

103103
```json
104104
{
105-
"Link": [
105+
"link": [
106106
[
107107
"url1",
108108
{

0 commit comments

Comments
 (0)