mirror of
https://github.com/cloudflare/cloudflare-docs.git
synced 2026-01-11 20:06:58 +00:00
[Docs Site] format yaml files (#16840)
* chore: format yml * chore: merge fixups * chore: merge fixups --------- Co-authored-by: kodster28 <kody@cloudflare.com>
This commit is contained in:
James Ross
GitHub
parent
77917992f8
commit
9b8d922b2a
112 changed files with 4054 additions and 4044 deletions
|
|
@ -1,5 +1,5 @@
|
|||
version: 2
|
||||
secret:
|
||||
ignored-paths:
|
||||
- 'assets/search.ts'
|
||||
- 'data/*.yml'
|
||||
- "assets/search.ts"
|
||||
- "data/*.yml"
|
||||
|
|
|
|||
6
.github/ISSUE_TEMPLATE/config.yml
vendored
6
.github/ISSUE_TEMPLATE/config.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
blank_issues_enabled: false
|
||||
contact_links:
|
||||
- name: Issue with your website
|
||||
url: https://developers.cloudflare.com/support/contacting-cloudflare-support/#methods-of-contacting-cloudflare-support
|
||||
url: https://developers.cloudflare.com/support/contacting-cloudflare-support/#methods-of-contacting-cloudflare-support
|
||||
about: If you need support with your website or Cloudflare applications, please contact Cloudflare through the relevant support channel.
|
||||
- name: Issue with Cloudflare 5XX errors
|
||||
url: https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#troubleshooting-cloudflare-5xx-errors--cloudflare-help-center
|
||||
url: https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#troubleshooting-cloudflare-5xx-errors--cloudflare-help-center
|
||||
about: If you are encountering a Cloudflare 5XX error, please read our troubleshooting documentation for 5XX errors.
|
||||
- name: Issue with Cloudflare Workers
|
||||
url: https://github.com/cloudflare/workers-sdk/issues/new/choose
|
||||
url: https://github.com/cloudflare/workers-sdk/issues/new/choose
|
||||
about: Issues relating to Cloudflare Workers should be made in the workers-sdk repo.
|
||||
|
|
|
|||
10
.github/actions/assign-issue/action.yml
vendored
10
.github/actions/assign-issue/action.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
name: 'Assign Issue Owner'
|
||||
description: 'Assign the issue to its product content owner.'
|
||||
name: "Assign Issue Owner"
|
||||
description: "Assign the issue to its product content owner."
|
||||
|
||||
inputs:
|
||||
GITHUB_TOKEN:
|
||||
description: 'token for repository access'
|
||||
description: "token for repository access"
|
||||
required: true
|
||||
|
||||
runs:
|
||||
using: 'node16'
|
||||
main: 'index.js'
|
||||
using: "node16"
|
||||
main: "index.js"
|
||||
|
|
|
|||
10
.github/actions/assign-pr/action.yml
vendored
10
.github/actions/assign-pr/action.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
name: 'Assign PR Owner'
|
||||
description: 'Assign the PR to its product content owner.'
|
||||
name: "Assign PR Owner"
|
||||
description: "Assign the PR to its product content owner."
|
||||
|
||||
inputs:
|
||||
GITHUB_TOKEN:
|
||||
description: 'token for repository access'
|
||||
description: "token for repository access"
|
||||
required: true
|
||||
|
||||
runs:
|
||||
using: 'node16'
|
||||
main: 'index.js'
|
||||
using: "node16"
|
||||
main: "index.js"
|
||||
|
|
|
|||
10
.github/actions/label-products/action.yml
vendored
10
.github/actions/label-products/action.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
name: 'Label products'
|
||||
description: 'Apply labels based on the product folders touched.'
|
||||
name: "Label products"
|
||||
description: "Apply labels based on the product folders touched."
|
||||
|
||||
inputs:
|
||||
GITHUB_TOKEN:
|
||||
description: 'token for repository access'
|
||||
description: "token for repository access"
|
||||
required: true
|
||||
|
||||
runs:
|
||||
using: 'node16'
|
||||
main: 'index.js'
|
||||
using: "node16"
|
||||
main: "index.js"
|
||||
|
|
|
|||
10
.github/actions/label-size/action.yml
vendored
10
.github/actions/label-size/action.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
name: 'Label size'
|
||||
description: 'Apply labels based on the size of the PR'
|
||||
name: "Label size"
|
||||
description: "Apply labels based on the size of the PR"
|
||||
|
||||
inputs:
|
||||
GITHUB_TOKEN:
|
||||
description: 'token for repository access'
|
||||
description: "token for repository access"
|
||||
required: true
|
||||
|
||||
runs:
|
||||
using: 'node16'
|
||||
main: 'index.js'
|
||||
using: "node16"
|
||||
main: "index.js"
|
||||
|
|
|
|||
10
.github/actions/show-changed-files/action.yml
vendored
10
.github/actions/show-changed-files/action.yml
vendored
|
|
@ -1,11 +1,11 @@
|
|||
name: 'Show changed files'
|
||||
description: 'Comment on the PR with before and after links to help isolate and review changes'
|
||||
name: "Show changed files"
|
||||
description: "Comment on the PR with before and after links to help isolate and review changes"
|
||||
|
||||
inputs:
|
||||
GITHUB_TOKEN:
|
||||
description: 'token for repository access'
|
||||
description: "token for repository access"
|
||||
required: true
|
||||
|
||||
runs:
|
||||
using: 'node16'
|
||||
main: 'index.js'
|
||||
using: "node16"
|
||||
main: "index.js"
|
||||
|
|
|
|||
|
|
@ -20,4 +20,3 @@ swap:
|
|||
hers: their
|
||||
sanity (?:check|test): check for completeness
|
||||
dummy: placeholder, sample, fake
|
||||
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@ message: "Merge conflict marker '%s' found. [Address the merge conflict](https:/
|
|||
level: error
|
||||
scope: raw
|
||||
raw:
|
||||
- '\n<<<<<<< .+\n|\n=======\n|\n>>>>>>> .+\n'
|
||||
- '\n<<<<<<< .+\n|\n=======\n|\n>>>>>>> .+\n'
|
||||
|
|
|
|||
2
.github/styles/cloudflare/Repetition.yml
vendored
2
.github/styles/cloudflare/Repetition.yml
vendored
|
|
@ -9,4 +9,4 @@ message: "**Warning**: Remove this duplicate word: '%s'."
|
|||
level: warning
|
||||
alpha: true
|
||||
tokens:
|
||||
- '[^\s]+'
|
||||
- '[^\s]+'
|
||||
|
|
|
|||
3
.github/workflows/anchor-link-audit.yml
vendored
3
.github/workflows/anchor-link-audit.yml
vendored
|
|
@ -6,7 +6,7 @@ name: Anchor link audit
|
|||
|
||||
on:
|
||||
schedule:
|
||||
- cron: "0 0 * * 0" # Run at 00:00 UTC every Sunday
|
||||
- cron: "0 0 * * 0" # Run at 00:00 UTC every Sunday
|
||||
workflow_dispatch:
|
||||
|
||||
jobs:
|
||||
|
|
@ -40,7 +40,6 @@ jobs:
|
|||
env:
|
||||
NODE_OPTIONS: "--max-old-space-size=4192"
|
||||
|
||||
|
||||
- name: Install dependencies
|
||||
run: curl https://htmltest.wjdp.uk | bash
|
||||
|
||||
|
|
|
|||
5
.github/workflows/api-links-crawl.yml
vendored
5
.github/workflows/api-links-crawl.yml
vendored
|
|
@ -6,7 +6,7 @@ name: Crawl API docs links
|
|||
|
||||
on:
|
||||
schedule:
|
||||
- cron: "0 0 * * 0" # Run at 00:00 UTC every Sunday
|
||||
- cron: "0 0 * * 0" # Run at 00:00 UTC every Sunday
|
||||
workflow_dispatch:
|
||||
|
||||
jobs:
|
||||
|
|
@ -51,6 +51,3 @@ jobs:
|
|||
-H "Accept: application/vnd.github+json" \
|
||||
"https://api.github.com/repos/cloudflare/cloudflare-docs/issues" \
|
||||
-d "{\"title\": \"Broken API docs links\", \"body\": \"The following API doc links are broken: ${EXPORTED_VARIABLE}\", \"assignees\": [\"kodster28\", \"haleycode\"]}"
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,6 @@ concurrency:
|
|||
cancel-in-progress: true
|
||||
|
||||
jobs:
|
||||
|
||||
flag_changed_filenames:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
|
|
|
|||
2
.github/workflows/issue-sync.yml
vendored
2
.github/workflows/issue-sync.yml
vendored
|
|
@ -15,7 +15,7 @@ jobs:
|
|||
- name: Set up Go
|
||||
uses: actions/setup-go@v4
|
||||
with:
|
||||
go-version-file: 'tools/go.mod'
|
||||
go-version-file: "tools/go.mod"
|
||||
- run: make tools
|
||||
- name: Set the issue number to sync
|
||||
run: |
|
||||
|
|
|
|||
2
.github/workflows/issue.yml
vendored
2
.github/workflows/issue.yml
vendored
|
|
@ -12,4 +12,4 @@ jobs:
|
|||
- uses: actions/checkout@v4
|
||||
- uses: ./.github/actions/assign-issue
|
||||
with:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
|
|
|||
3
.github/workflows/label-pr.yml
vendored
3
.github/workflows/label-pr.yml
vendored
|
|
@ -11,7 +11,6 @@ concurrency:
|
|||
cancel-in-progress: true
|
||||
|
||||
jobs:
|
||||
|
||||
label_products:
|
||||
name: Label products
|
||||
runs-on: ubuntu-latest
|
||||
|
|
@ -30,4 +29,4 @@ jobs:
|
|||
- uses: ./.github/actions/label-size
|
||||
with:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
continue-on-error: true
|
||||
continue-on-error: true
|
||||
|
|
|
|||
2
.github/workflows/no-response.yml
vendored
2
.github/workflows/no-response.yml
vendored
|
|
@ -13,7 +13,7 @@ on:
|
|||
issue_comment:
|
||||
types: [created]
|
||||
schedule:
|
||||
- cron: '0 0 * * *' # Runs at 12:00 AM UTC every day
|
||||
- cron: "0 0 * * *" # Runs at 12:00 AM UTC every day
|
||||
|
||||
jobs:
|
||||
noResponse:
|
||||
|
|
|
|||
2
.github/workflows/pr.yml
vendored
2
.github/workflows/pr.yml
vendored
|
|
@ -17,4 +17,4 @@ jobs:
|
|||
- uses: actions/checkout@v4
|
||||
- uses: ./.github/actions/assign-pr
|
||||
with:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
|
|
|||
2
.github/workflows/show-changed-files.yml
vendored
2
.github/workflows/show-changed-files.yml
vendored
|
|
@ -5,7 +5,7 @@ name: Show Changed Files
|
|||
# **Who does it impact**: PCX team
|
||||
|
||||
on:
|
||||
issue_comment:
|
||||
issue_comment:
|
||||
types:
|
||||
- created
|
||||
- edited
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
DirectoryPath: "dist"
|
||||
EnforceHTTPS: false
|
||||
IgnoreURLs:
|
||||
- "/api/*"
|
||||
- "/api/*"
|
||||
CheckLinks: true
|
||||
CheckImages: false
|
||||
CheckScripts: false
|
||||
|
|
@ -9,4 +9,4 @@ CheckGeneric: false
|
|||
CheckExternal: false
|
||||
IgnoreInternalEmptyHash: true
|
||||
IgnoreEmptyHref: true
|
||||
IgnoreDirectoryMissingTrailingSlash: true
|
||||
IgnoreDirectoryMissingTrailingSlash: true
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
openapi: 3.0.0
|
||||
info:
|
||||
title: Cloudflare Calls API
|
||||
version: '1.0'
|
||||
version: "1.0"
|
||||
externalDocs:
|
||||
description: Find out more about Cloudflare Calls
|
||||
url: https://developers.cloudflare.com/calls/
|
||||
|
|
@ -23,7 +23,7 @@ paths:
|
|||
required: true
|
||||
description: WebRTC application ID
|
||||
responses:
|
||||
'201':
|
||||
"201":
|
||||
description: Created
|
||||
headers:
|
||||
vary:
|
||||
|
|
@ -34,7 +34,7 @@ paths:
|
|||
application/json:
|
||||
schema:
|
||||
allOf:
|
||||
- $ref: '#/components/schemas/NewSessionResponse'
|
||||
- $ref: "#/components/schemas/NewSessionResponse"
|
||||
- example:
|
||||
sessionId: e017a2629c754fedc1f7d8587e06d126
|
||||
/apps/{appId}/sessions/{sessionId}/tracks/new:
|
||||
|
|
@ -46,7 +46,7 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/TracksRequest'
|
||||
$ref: "#/components/schemas/TracksRequest"
|
||||
examples:
|
||||
local_tracks:
|
||||
description: Share a track to be played by remote peers
|
||||
|
|
@ -66,7 +66,7 @@ paths:
|
|||
type: offer
|
||||
tracks:
|
||||
- location: local
|
||||
mid: '4'
|
||||
mid: "4"
|
||||
trackName: 1a037563-c35c-4bf6-a9ee-2b474cbb9a51
|
||||
remote_tracks:
|
||||
description: Play a track from a remote peer
|
||||
|
|
@ -91,7 +91,7 @@ paths:
|
|||
required: true
|
||||
description: Current PeerConnection session ID
|
||||
responses:
|
||||
'200':
|
||||
"200":
|
||||
description: OK
|
||||
headers:
|
||||
vary:
|
||||
|
|
@ -101,14 +101,14 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/TracksResponse'
|
||||
$ref: "#/components/schemas/TracksResponse"
|
||||
examples:
|
||||
local_tracks:
|
||||
value:
|
||||
requiresImmediateRenegotiation: false
|
||||
tracks:
|
||||
- trackName: 1a037563-c35c-4bf6-a9ee-2b474cbb9a51
|
||||
mid: '4'
|
||||
- trackName: 1a037563-c35c-4bf6-a9ee-2b474cbb9a51
|
||||
mid: "4"
|
||||
sessionDescription:
|
||||
sdp: |
|
||||
v=0
|
||||
|
|
@ -128,7 +128,7 @@ paths:
|
|||
tracks:
|
||||
- sessionId: 2a45361d5fd7cc14eface0587c276c94
|
||||
trackName: 2e037563-a35d-4bf6-a9ee-2d474cbb9a58
|
||||
mid: '7'
|
||||
mid: "7"
|
||||
sessionDescription:
|
||||
sdp: |
|
||||
v=0
|
||||
|
|
@ -153,7 +153,7 @@ paths:
|
|||
schema:
|
||||
properties:
|
||||
sessionDescription:
|
||||
$ref: '#/components/schemas/SessionDescription'
|
||||
$ref: "#/components/schemas/SessionDescription"
|
||||
example:
|
||||
sessionDescription:
|
||||
sdp: |
|
||||
|
|
@ -183,7 +183,7 @@ paths:
|
|||
type: string
|
||||
required: true
|
||||
responses:
|
||||
'200':
|
||||
"200":
|
||||
description: OK
|
||||
headers:
|
||||
vary:
|
||||
|
|
@ -193,7 +193,7 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/SessionDescription'
|
||||
$ref: "#/components/schemas/SessionDescription"
|
||||
example: {}
|
||||
/apps/{appId}/sessions/{sessionId}/tracks/close:
|
||||
put:
|
||||
|
|
@ -205,10 +205,10 @@ paths:
|
|||
application/json:
|
||||
schema:
|
||||
allOf:
|
||||
- $ref: '#/components/schemas/CloseTracksRequest'
|
||||
- $ref: "#/components/schemas/CloseTracksRequest"
|
||||
- example:
|
||||
tracks:
|
||||
- mid: '7'
|
||||
- mid: "7"
|
||||
sessionDescription:
|
||||
sdp: |
|
||||
v=0
|
||||
|
|
@ -238,7 +238,7 @@ paths:
|
|||
type: string
|
||||
required: true
|
||||
responses:
|
||||
'200':
|
||||
"200":
|
||||
description: OK
|
||||
headers:
|
||||
vary:
|
||||
|
|
@ -248,7 +248,7 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/CloseTracksResponse'
|
||||
$ref: "#/components/schemas/CloseTracksResponse"
|
||||
example:
|
||||
sessionDescription:
|
||||
sdp: |
|
||||
|
|
@ -265,7 +265,7 @@ paths:
|
|||
type: answer
|
||||
requiresImmediateRenegotiation: false
|
||||
tracks:
|
||||
- mid: '7'
|
||||
- mid: "7"
|
||||
/apps/{appId}/sessions/{sessionId}:
|
||||
get:
|
||||
tags:
|
||||
|
|
@ -286,7 +286,7 @@ paths:
|
|||
type: string
|
||||
required: true
|
||||
responses:
|
||||
'200':
|
||||
"200":
|
||||
description: OK
|
||||
headers:
|
||||
vary:
|
||||
|
|
@ -296,15 +296,15 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: '#/components/schemas/GetSessionStateResponse'
|
||||
$ref: "#/components/schemas/GetSessionStateResponse"
|
||||
example:
|
||||
tracks:
|
||||
- location: local
|
||||
mid: '2'
|
||||
mid: "2"
|
||||
trackName: 1a037563-c35c-4bf6-a9ee-2b474cbb9a51
|
||||
status: active
|
||||
- location: remote
|
||||
mid: '7'
|
||||
mid: "7"
|
||||
sessionId: 2a45361d5fd7cc14eface0587c276c94
|
||||
trackName: 2e037563-a35d-4bf6-a9ee-2d474cbb9a58
|
||||
status: active
|
||||
|
|
@ -350,14 +350,14 @@ components:
|
|||
type: string
|
||||
description: mid associated to the track's transceiver to close
|
||||
TracksRequest:
|
||||
type: object
|
||||
properties:
|
||||
sessionDescription:
|
||||
$ref: "#/components/schemas/SessionDescription"
|
||||
tracks:
|
||||
type: array
|
||||
items:
|
||||
$ref: "#/components/schemas/TrackObject"
|
||||
type: object
|
||||
properties:
|
||||
sessionDescription:
|
||||
$ref: "#/components/schemas/SessionDescription"
|
||||
tracks:
|
||||
type: array
|
||||
items:
|
||||
$ref: "#/components/schemas/TrackObject"
|
||||
TracksResponse:
|
||||
type: object
|
||||
properties:
|
||||
|
|
@ -444,4 +444,4 @@ components:
|
|||
enum:
|
||||
- active
|
||||
- inactive
|
||||
- waiting
|
||||
- waiting
|
||||
|
|
|
|||
|
|
@ -5,59 +5,59 @@ productLink: "/cloudflare-one/applications/configure-apps/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-08-26'
|
||||
title: Reduce automatic seat deprovisioning minimum to 1 month, down from 2 months.
|
||||
description: |-
|
||||
Admins can now configure Zero Trust seats to [automatically expire](/cloudflare-one/identity/users/seat-management/#enable-seat-expiration) after 1 month of user inactivity. The previous minimum was 2 months.
|
||||
- publish_date: '2024-06-06'
|
||||
title: Scalability improvements to the App Launcher
|
||||
description: |-
|
||||
Applications now load more quickly for customers with a large number of applications or complex policies.
|
||||
- publish_date: '2024-04-28'
|
||||
title: Add option to bypass CORS to origin server
|
||||
description: |-
|
||||
Access admins can [defer all CORS enforcement to their origin server](/cloudflare-one/identity/authorization-cookie/cors/#bypass-options-requests-to-origin) for specific Access applications.
|
||||
- publish_date: '2024-04-15'
|
||||
title: Zero Trust User identity audit logs
|
||||
description: |-
|
||||
All user identity changes via SCIM or Authentication events are logged against a user's registry identity.
|
||||
- publish_date: '2024-02-22'
|
||||
title: Access for SaaS OIDC Support
|
||||
description: |-
|
||||
Access for SaaS applications can be setup with OIDC as an authentication method. OIDC and SAML 2.0 are now both fully supported.
|
||||
- publish_date: '2024-02-22'
|
||||
title: WARP as an identity source for Access
|
||||
description: |-
|
||||
Allow users to log in to Access applications with their WARP session identity. Users need to reauthenticate based on default session durations. WARP authentication identity must be turned on in your device enrollment permissions and can be enabled on a per application basis.
|
||||
- publish_date: '2023-12-20'
|
||||
title: Unique Entity IDs in Access for SaaS
|
||||
description: |-
|
||||
All new Access for SaaS applications have unique Entity IDs. This allows for multiple integrations with the same SaaS provider if required. The unique Entity ID has the application audience tag appended. Existing apps are unchanged.
|
||||
- publish_date: '2023-12-15'
|
||||
title: Default relay state support in Access for SaaS
|
||||
description: |-
|
||||
Allows Access admins to set a default relay state on Access for SaaS apps.
|
||||
- publish_date: '2023-09-15'
|
||||
title: App launcher supports tags and filters
|
||||
description: |-
|
||||
Access admins can now tag applications and allow users to filter by those tags in the App Launcher.
|
||||
- publish_date: '2023-09-15'
|
||||
title: App launcher customization
|
||||
description: |-
|
||||
Allow Access admins to configure the App Launcher page within Zero Trust.
|
||||
- publish_date: '2023-09-15'
|
||||
title: View active Access user identities in the dashboard and API
|
||||
description: |-
|
||||
Access admins can now view the full contents of a user's identity and device information for all active application sessions.
|
||||
- publish_date: '2023-09-08'
|
||||
title: Custom OIDC claims for named IdPs
|
||||
description: |-
|
||||
Access admins can now add custom claims to the existing named IdP providers. Previously this was locked to the generic OIDC provider.
|
||||
- publish_date: '2023-08-02'
|
||||
title: Azure AD authentication contexts
|
||||
description: |-
|
||||
Support Azure AD authentication contexts directly in Access policies.
|
||||
- publish_date: '2023-06-23'
|
||||
title: Custom block pages for Access applications
|
||||
description: |-
|
||||
Allow Access admins to customize the block pages presented by Access to end users.
|
||||
- publish_date: "2024-08-26"
|
||||
title: Reduce automatic seat deprovisioning minimum to 1 month, down from 2 months.
|
||||
description: |-
|
||||
Admins can now configure Zero Trust seats to [automatically expire](/cloudflare-one/identity/users/seat-management/#enable-seat-expiration) after 1 month of user inactivity. The previous minimum was 2 months.
|
||||
- publish_date: "2024-06-06"
|
||||
title: Scalability improvements to the App Launcher
|
||||
description: |-
|
||||
Applications now load more quickly for customers with a large number of applications or complex policies.
|
||||
- publish_date: "2024-04-28"
|
||||
title: Add option to bypass CORS to origin server
|
||||
description: |-
|
||||
Access admins can [defer all CORS enforcement to their origin server](/cloudflare-one/identity/authorization-cookie/cors/#bypass-options-requests-to-origin) for specific Access applications.
|
||||
- publish_date: "2024-04-15"
|
||||
title: Zero Trust User identity audit logs
|
||||
description: |-
|
||||
All user identity changes via SCIM or Authentication events are logged against a user's registry identity.
|
||||
- publish_date: "2024-02-22"
|
||||
title: Access for SaaS OIDC Support
|
||||
description: |-
|
||||
Access for SaaS applications can be setup with OIDC as an authentication method. OIDC and SAML 2.0 are now both fully supported.
|
||||
- publish_date: "2024-02-22"
|
||||
title: WARP as an identity source for Access
|
||||
description: |-
|
||||
Allow users to log in to Access applications with their WARP session identity. Users need to reauthenticate based on default session durations. WARP authentication identity must be turned on in your device enrollment permissions and can be enabled on a per application basis.
|
||||
- publish_date: "2023-12-20"
|
||||
title: Unique Entity IDs in Access for SaaS
|
||||
description: |-
|
||||
All new Access for SaaS applications have unique Entity IDs. This allows for multiple integrations with the same SaaS provider if required. The unique Entity ID has the application audience tag appended. Existing apps are unchanged.
|
||||
- publish_date: "2023-12-15"
|
||||
title: Default relay state support in Access for SaaS
|
||||
description: |-
|
||||
Allows Access admins to set a default relay state on Access for SaaS apps.
|
||||
- publish_date: "2023-09-15"
|
||||
title: App launcher supports tags and filters
|
||||
description: |-
|
||||
Access admins can now tag applications and allow users to filter by those tags in the App Launcher.
|
||||
- publish_date: "2023-09-15"
|
||||
title: App launcher customization
|
||||
description: |-
|
||||
Allow Access admins to configure the App Launcher page within Zero Trust.
|
||||
- publish_date: "2023-09-15"
|
||||
title: View active Access user identities in the dashboard and API
|
||||
description: |-
|
||||
Access admins can now view the full contents of a user's identity and device information for all active application sessions.
|
||||
- publish_date: "2023-09-08"
|
||||
title: Custom OIDC claims for named IdPs
|
||||
description: |-
|
||||
Access admins can now add custom claims to the existing named IdP providers. Previously this was locked to the generic OIDC provider.
|
||||
- publish_date: "2023-08-02"
|
||||
title: Azure AD authentication contexts
|
||||
description: |-
|
||||
Support Azure AD authentication contexts directly in Access policies.
|
||||
- publish_date: "2023-06-23"
|
||||
title: Custom block pages for Access applications
|
||||
description: |-
|
||||
Allow Access admins to customize the block pages presented by Access to end users.
|
||||
|
|
|
|||
|
|
@ -5,440 +5,440 @@ productLink: "/fundamentals/"
|
|||
productArea: Core platform
|
||||
productAreaLink: /fundamentals/reference/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2025-01-15'
|
||||
title: "Firewall Rules API and Filters API"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
- publish_date: "2025-01-15"
|
||||
title: "Firewall Rules API and Filters API"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
|
||||
The Firewall Rules API and the Filters API are deprecated, since Firewall Rules was deprecated in favor of [WAF custom rules](/waf/custom-rules/). Refer to [Firewall Rules to WAF custom rules migration](/waf/reference/migration-guides/firewall-rules-to-custom-rules/) for more information about this change.
|
||||
The Firewall Rules API and the Filters API are deprecated, since Firewall Rules was deprecated in favor of [WAF custom rules](/waf/custom-rules/). Refer to [Firewall Rules to WAF custom rules migration](/waf/reference/migration-guides/firewall-rules-to-custom-rules/) for more information about this change.
|
||||
|
||||
Deprecated APIs:
|
||||
Deprecated APIs:
|
||||
|
||||
- `GET /zones/:zone_id/firewall/rules`
|
||||
- `POST /zones/:zone_id/firewall/rules`
|
||||
- `PATCH /zones/:zone_id/firewall/rules`
|
||||
- `PUT /zones/:zone_id/firewall/rules`
|
||||
- `DELETE /zones/:zone_id/firewall/rules`
|
||||
- `GET /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `PATCH /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `PUT /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `DELETE /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `GET /zones/:zone_id/filters`
|
||||
- `POST /zones/:zone_id/filters`
|
||||
- `PUT /zones/:zone_id/filters`
|
||||
- `DELETE /zones/:zone_id/filters`
|
||||
- `GET /zones/:zone_id/filters/:filter_id`
|
||||
- `PUT /zones/:zone_id/filters/:filter_id`
|
||||
- `DELETE /zones/:zone_id/filters/:filter_id`
|
||||
- `GET /zones/:zone_id/firewall/rules`
|
||||
- `POST /zones/:zone_id/firewall/rules`
|
||||
- `PATCH /zones/:zone_id/firewall/rules`
|
||||
- `PUT /zones/:zone_id/firewall/rules`
|
||||
- `DELETE /zones/:zone_id/firewall/rules`
|
||||
- `GET /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `PATCH /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `PUT /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `DELETE /zones/:zone_id/firewall/rules/:rule_id`
|
||||
- `GET /zones/:zone_id/filters`
|
||||
- `POST /zones/:zone_id/filters`
|
||||
- `PUT /zones/:zone_id/filters`
|
||||
- `DELETE /zones/:zone_id/filters`
|
||||
- `GET /zones/:zone_id/filters/:filter_id`
|
||||
- `PUT /zones/:zone_id/filters/:filter_id`
|
||||
- `DELETE /zones/:zone_id/filters/:filter_id`
|
||||
|
||||
Replacement: [WAF custom rules](/waf/custom-rules/)
|
||||
Replacement: [WAF custom rules](/waf/custom-rules/)
|
||||
|
||||
- publish_date: '2025-01-15'
|
||||
title: "WAF managed rules APIs (previous version)"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
- publish_date: "2025-01-15"
|
||||
title: "WAF managed rules APIs (previous version)"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
|
||||
The APIs for managing WAF managed rules (previous version) — namely for managing packages, rule groups, rules, and overrides — are deprecated in favor of [WAF Managed Rules](/waf/managed-rules/). Refer to [WAF Managed Rules migration](/waf/reference/migration-guides/waf-managed-rules-migration/) for more information about this change.
|
||||
|
||||
Deprecated APIs:
|
||||
The APIs for managing WAF managed rules (previous version) — namely for managing packages, rule groups, rules, and overrides — are deprecated in favor of [WAF Managed Rules](/waf/managed-rules/). Refer to [WAF Managed Rules migration](/waf/reference/migration-guides/waf-managed-rules-migration/) for more information about this change.
|
||||
|
||||
- `GET /zones/:zone_id/firewall/waf/packages`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/groups`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/groups/:group_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id/groups/:group_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/rules`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/rules/:rule_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id/rules/:rule_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/overrides`
|
||||
- `POST /zones/:zone_id/firewall/waf/overrides`
|
||||
- `GET /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
- `PUT /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
- `DELETE /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
Deprecated APIs:
|
||||
|
||||
Replacement: [WAF Managed Rules](/waf/managed-rules/) (new version)
|
||||
- `GET /zones/:zone_id/firewall/waf/packages`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/groups`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/groups/:group_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id/groups/:group_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/rules`
|
||||
- `GET /zones/:zone_id/firewall/waf/packages/:package_id/rules/:rule_id`
|
||||
- `PATCH /zones/:zone_id/firewall/waf/packages/:package_id/rules/:rule_id`
|
||||
- `GET /zones/:zone_id/firewall/waf/overrides`
|
||||
- `POST /zones/:zone_id/firewall/waf/overrides`
|
||||
- `GET /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
- `PUT /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
- `DELETE /zones/:zone_id/firewall/waf/overrides/:override_id`
|
||||
|
||||
- publish_date: '2025-01-15'
|
||||
title: "Rate Limiting API (previous version)"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
Replacement: [WAF Managed Rules](/waf/managed-rules/) (new version)
|
||||
|
||||
The Rate Limiting API is deprecated, since the previous version of rate limiting rules was deprecated in favor of the new [rate limiting rules](/waf/rate-limiting-rules/) based on the Ruleset Engine. Refer to [Rate limiting (previous version) deprecation notice](/waf/reference/migration-guides/old-rate-limiting-deprecation/) for more information about this change.
|
||||
- publish_date: "2025-01-15"
|
||||
title: "Rate Limiting API (previous version)"
|
||||
description: |-
|
||||
Deprecation date: January 15, 2025
|
||||
|
||||
Deprecated API:
|
||||
The Rate Limiting API is deprecated, since the previous version of rate limiting rules was deprecated in favor of the new [rate limiting rules](/waf/rate-limiting-rules/) based on the Ruleset Engine. Refer to [Rate limiting (previous version) deprecation notice](/waf/reference/migration-guides/old-rate-limiting-deprecation/) for more information about this change.
|
||||
|
||||
- `GET /zones/:zone_id/rate_limits`
|
||||
- `POST /zones/:zone_id/rate_limits`
|
||||
- `GET /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
- `PUT /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
- `DELETE /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
Deprecated API:
|
||||
|
||||
Replacement: [Rate limiting rules](/waf/rate-limiting-rules/) (new version)
|
||||
|
||||
- publish_date: '2024-11-30'
|
||||
title: "Zone information in individual DNS records"
|
||||
description: |-
|
||||
Deprecation date: November 30, 2024
|
||||
- `GET /zones/:zone_id/rate_limits`
|
||||
- `POST /zones/:zone_id/rate_limits`
|
||||
- `GET /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
- `PUT /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
- `DELETE /zones/:zone_id/rate_limits/:rate_limit_id`
|
||||
|
||||
Currently, each individual DNS record returned by the API contains information about the zone it is on, specifically the zone ID and name.
|
||||
Replacement: [Rate limiting rules](/waf/rate-limiting-rules/) (new version)
|
||||
|
||||
```json
|
||||
{
|
||||
"result": [
|
||||
{
|
||||
// ...
|
||||
"zone_id": "ab922473c42f4e50819d7c1c9b81b16b",
|
||||
"zone_name": "example.com"
|
||||
}
|
||||
],
|
||||
// ...
|
||||
}
|
||||
```
|
||||
- publish_date: "2024-11-30"
|
||||
title: "Zone information in individual DNS records"
|
||||
description: |-
|
||||
Deprecation date: November 30, 2024
|
||||
|
||||
This information is redundant because both affected API routes are already within the zone scope. In particular, the zone ID will already be known to any user of these routes because it appears in the URL. The zone name can be retrieved by making a `GET` request to `/zones/:zone_id` if it is necessary.
|
||||
Currently, each individual DNS record returned by the API contains information about the zone it is on, specifically the zone ID and name.
|
||||
|
||||
After November 30th, 2024, Cloudflare will stop including the `zone_id` and `zone_name` fields on individual DNS records in API responses. These fields are currently ignored when sent to the API as part of a request body, so no changes to request bodies are required.
|
||||
```json
|
||||
{
|
||||
"result": [
|
||||
{
|
||||
// ...
|
||||
"zone_id": "ab922473c42f4e50819d7c1c9b81b16b",
|
||||
"zone_name": "example.com"
|
||||
}
|
||||
],
|
||||
// ...
|
||||
}
|
||||
```
|
||||
|
||||
Modified API:
|
||||
This information is redundant because both affected API routes are already within the zone scope. In particular, the zone ID will already be known to any user of these routes because it appears in the URL. The zone name can be retrieved by making a `GET` request to `/zones/:zone_id` if it is necessary.
|
||||
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
After November 30th, 2024, Cloudflare will stop including the `zone_id` and `zone_name` fields on individual DNS records in API responses. These fields are currently ignored when sent to the API as part of a request body, so no changes to request bodies are required.
|
||||
|
||||
- publish_date: '2024-10-01'
|
||||
title: "DNS Records: Error chains for DNS validation errors"
|
||||
description: |-
|
||||
Deprecation date: October 1, 2024
|
||||
Modified API:
|
||||
|
||||
Cloudflare is making a minor change to the representation of certain errors when creating DNS records. Currently, when the DNS record to be created is invalid, an error similar to the following may be returned:
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
|
||||
```txt
|
||||
{
|
||||
"result": null,
|
||||
"success": false,
|
||||
"errors": [
|
||||
{
|
||||
"code": 1004,
|
||||
"message": "DNS Validation Error",
|
||||
"error_chain": [
|
||||
{
|
||||
"code": 9999,
|
||||
"message": "This is an example."
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"messages": []
|
||||
}
|
||||
```
|
||||
- publish_date: "2024-10-01"
|
||||
title: "DNS Records: Error chains for DNS validation errors"
|
||||
description: |-
|
||||
Deprecation date: October 1, 2024
|
||||
|
||||
After October 1st, 2024, the `error_chain` will be omitted, returning the root cause directly without wrapping it in another "DNS Validation Error" error:
|
||||
Cloudflare is making a minor change to the representation of certain errors when creating DNS records. Currently, when the DNS record to be created is invalid, an error similar to the following may be returned:
|
||||
|
||||
```txt
|
||||
{
|
||||
"result": null,
|
||||
"success": false,
|
||||
"errors": [
|
||||
{
|
||||
"code": 9999,
|
||||
"message": "This is an example."
|
||||
}
|
||||
],
|
||||
"messages": []
|
||||
}
|
||||
```
|
||||
```txt
|
||||
{
|
||||
"result": null,
|
||||
"success": false,
|
||||
"errors": [
|
||||
{
|
||||
"code": 1004,
|
||||
"message": "DNS Validation Error",
|
||||
"error_chain": [
|
||||
{
|
||||
"code": 9999,
|
||||
"message": "This is an example."
|
||||
}
|
||||
]
|
||||
}
|
||||
],
|
||||
"messages": []
|
||||
}
|
||||
```
|
||||
|
||||
- publish_date: '2024-09-13'
|
||||
title: "Legacy DNS Settings Endpoints"
|
||||
description: |-
|
||||
Deprecation date: September 13, 2024
|
||||
After October 1st, 2024, the `error_chain` will be omitted, returning the root cause directly without wrapping it in another "DNS Validation Error" error:
|
||||
|
||||
The dedicated endpoints for DNS settings `use_apex_ns` and `secondary_overrides` are being deprecated.
|
||||
```txt
|
||||
{
|
||||
"result": null,
|
||||
"success": false,
|
||||
"errors": [
|
||||
{
|
||||
"code": 9999,
|
||||
"message": "This is an example."
|
||||
}
|
||||
],
|
||||
"messages": []
|
||||
}
|
||||
```
|
||||
|
||||
Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-a-zone-list-dns-settings) and [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoints to manage these settings.
|
||||
- publish_date: "2024-09-13"
|
||||
title: "Legacy DNS Settings Endpoints"
|
||||
description: |-
|
||||
Deprecation date: September 13, 2024
|
||||
|
||||
- Instead of the `.../use_apex_ns` endpoint, use the `multi_provider` field.
|
||||
- Instead of the `.../secondary_overrides` endpoint, use the `secondary_overrides` field.
|
||||
The dedicated endpoints for DNS settings `use_apex_ns` and `secondary_overrides` are being deprecated.
|
||||
|
||||
Deprecated APIs:
|
||||
Instead, use the [Show DNS Settings](/api/operations/dns-settings-for-a-zone-list-dns-settings) and [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoints to manage these settings.
|
||||
|
||||
- `GET /zones/:zone_id/dns_settings/use_apex_ns`
|
||||
- `PATCH /zones/:zone_id/dns_settings/use_apex_ns`
|
||||
- `GET /zones/:zone_id/dns_settings/secondary_overrides`
|
||||
- `PATCH /zones/:zone_id/dns_settings/secondary_overrides`
|
||||
- Instead of the `.../use_apex_ns` endpoint, use the `multi_provider` field.
|
||||
- Instead of the `.../secondary_overrides` endpoint, use the `secondary_overrides` field.
|
||||
|
||||
- publish_date: '2024-08-15'
|
||||
title: "Brotli"
|
||||
description: |-
|
||||
Deprecation date: August 15, 2024
|
||||
Deprecated APIs:
|
||||
|
||||
The Brotli setting and its API endpoints are deprecated. After the end of life date, Brotli compression will be enabled by default for all zones.
|
||||
- `GET /zones/:zone_id/dns_settings/use_apex_ns`
|
||||
- `PATCH /zones/:zone_id/dns_settings/use_apex_ns`
|
||||
- `GET /zones/:zone_id/dns_settings/secondary_overrides`
|
||||
- `PATCH /zones/:zone_id/dns_settings/secondary_overrides`
|
||||
|
||||
Deprecated APIs:
|
||||
- publish_date: "2024-08-15"
|
||||
title: "Brotli"
|
||||
description: |-
|
||||
Deprecation date: August 15, 2024
|
||||
|
||||
- `GET /zones/:zone_id/settings/brotli`
|
||||
- `PATCH /zones/:zone_id/settings/brotli`
|
||||
The Brotli setting and its API endpoints are deprecated. After the end of life date, Brotli compression will be enabled by default for all zones.
|
||||
|
||||
Enterprise customers can override Cloudflare's default compression behavior using [Compression Rules](/rules/compression-rules/).
|
||||
Deprecated APIs:
|
||||
|
||||
- publish_date: '2024-08-05'
|
||||
title: "Auto Minify"
|
||||
description: |-
|
||||
Deprecation date: August 5, 2024
|
||||
- `GET /zones/:zone_id/settings/brotli`
|
||||
- `PATCH /zones/:zone_id/settings/brotli`
|
||||
|
||||
The Auto Minify API endpoints are deprecated since the Auto Minify feature was deprecated.
|
||||
Enterprise customers can override Cloudflare's default compression behavior using [Compression Rules](/rules/compression-rules/).
|
||||
|
||||
Deprecated APIs:
|
||||
- publish_date: "2024-08-05"
|
||||
title: "Auto Minify"
|
||||
description: |-
|
||||
Deprecation date: August 5, 2024
|
||||
|
||||
- `GET /zones/:zone_id/settings/minify`
|
||||
- `PATCH /zones/:zone_id/settings/minify`
|
||||
The Auto Minify API endpoints are deprecated since the Auto Minify feature was deprecated.
|
||||
|
||||
- publish_date: '2024-07-14'
|
||||
title: "DNS Records: 'locked' Field"
|
||||
description: |-
|
||||
Deprecation date: July 14, 2024
|
||||
Deprecated APIs:
|
||||
|
||||
The `"locked"` field of DNS records in API responses is unused and has been guaranteed to always be `false` for more than a year. This deprecation means that the field will be omitted from API responses entirely. If received from a client, the field will continue to be ignored, just as it is today.
|
||||
- `GET /zones/:zone_id/settings/minify`
|
||||
- `PATCH /zones/:zone_id/settings/minify`
|
||||
|
||||
Modified API:
|
||||
- publish_date: "2024-07-14"
|
||||
title: "DNS Records: 'locked' Field"
|
||||
description: |-
|
||||
Deprecation date: July 14, 2024
|
||||
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
The `"locked"` field of DNS records in API responses is unused and has been guaranteed to always be `false` for more than a year. This deprecation means that the field will be omitted from API responses entirely. If received from a client, the field will continue to be ignored, just as it is today.
|
||||
|
||||
- publish_date: '2024-06-30'
|
||||
title: "Mobile redirect"
|
||||
description: |-
|
||||
Deprecation date: June 30, 2024
|
||||
Modified API:
|
||||
|
||||
This endpoint and its related APIs are deprecated in favor of [Single Redirects](/rules/url-forwarding/single-redirects/). Refer to [Perform mobile redirects](/rules/url-forwarding/examples/perform-mobile-redirects/) to migrate Mobile Redirect to Redirect Rules.
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
|
||||
Deprecated API:
|
||||
- publish_date: "2024-06-30"
|
||||
title: "Mobile redirect"
|
||||
description: |-
|
||||
Deprecation date: June 30, 2024
|
||||
|
||||
- `GET /zones/:zone_identifier/settings/mobile_redirect`
|
||||
- `PATCH /zones/:zone_identifier/settings/mobile_redirect`
|
||||
This endpoint and its related APIs are deprecated in favor of [Single Redirects](/rules/url-forwarding/single-redirects/). Refer to [Perform mobile redirects](/rules/url-forwarding/examples/perform-mobile-redirects/) to migrate Mobile Redirect to Redirect Rules.
|
||||
|
||||
Replacement: [Single Redirects](/rules/url-forwarding/single-redirects/)
|
||||
Deprecated API:
|
||||
|
||||
- publish_date: '2024-06-14'
|
||||
title: "Server-side Excludes"
|
||||
description: |-
|
||||
Deprecation date: June 14, 2024
|
||||
- `GET /zones/:zone_identifier/settings/mobile_redirect`
|
||||
- `PATCH /zones/:zone_identifier/settings/mobile_redirect`
|
||||
|
||||
The Server-side Excludes feature and its API endpoints are deprecated.
|
||||
Replacement: [Single Redirects](/rules/url-forwarding/single-redirects/)
|
||||
|
||||
Deprecated APIs:
|
||||
- publish_date: "2024-06-14"
|
||||
title: "Server-side Excludes"
|
||||
description: |-
|
||||
Deprecation date: June 14, 2024
|
||||
|
||||
- `GET /zones/:zone_id/settings/server_side_exclude`
|
||||
- `PATCH /zones/:zone_id/settings/server_side_exclude`
|
||||
The Server-side Excludes feature and its API endpoints are deprecated.
|
||||
|
||||
- publish_date: '2024-05-31'
|
||||
title: "Name-Related Data Fields on SRV (DNS) Records"
|
||||
description: |-
|
||||
Deprecation date: May 31, 2024
|
||||
Deprecated APIs:
|
||||
|
||||
The name of an SRV record normally consists of three parts: the service (e.g., `_xmpp`), the protocol (e.g., `_tcp`), and the base name (`example.com`).
|
||||
|
||||
The complete name would then be, e.g., `_xmpp._tcp.example.com`.
|
||||
- `GET /zones/:zone_id/settings/server_side_exclude`
|
||||
- `PATCH /zones/:zone_id/settings/server_side_exclude`
|
||||
|
||||
When interacting with DNS records through the [API](/api/operations/dns-records-for-a-zone-create-dns-record), SRV records contain both a full `name` as well as a `data` map containing the individual components of the name:
|
||||
- publish_date: "2024-05-31"
|
||||
title: "Name-Related Data Fields on SRV (DNS) Records"
|
||||
description: |-
|
||||
Deprecation date: May 31, 2024
|
||||
|
||||
```txt
|
||||
{
|
||||
"name": "_xmpp._tcp.example.com",
|
||||
"data": {
|
||||
"service": "_xmpp",
|
||||
"proto": "_tcp",
|
||||
"name": "example.com",
|
||||
The name of an SRV record normally consists of three parts: the service (e.g., `_xmpp`), the protocol (e.g., `_tcp`), and the base name (`example.com`).
|
||||
|
||||
The complete name would then be, e.g., `_xmpp._tcp.example.com`.
|
||||
|
||||
When interacting with DNS records through the [API](/api/operations/dns-records-for-a-zone-create-dns-record), SRV records contain both a full `name` as well as a `data` map containing the individual components of the name:
|
||||
|
||||
```txt
|
||||
{
|
||||
"name": "_xmpp._tcp.example.com",
|
||||
"data": {
|
||||
"service": "_xmpp",
|
||||
"proto": "_tcp",
|
||||
"name": "example.com",
|
||||
...
|
||||
},
|
||||
...
|
||||
},
|
||||
...
|
||||
}
|
||||
```
|
||||
}
|
||||
```
|
||||
|
||||
We are deprecating the `service`, `proto` and `name` fields *within* the `data` map in favor of the `name` field *outside* the data map, which is the same name field that's used by all other record types.
|
||||
We are deprecating the `service`, `proto` and `name` fields *within* the `data` map in favor of the `name` field *outside* the data map, which is the same name field that's used by all other record types.
|
||||
|
||||
Before the end of life date, please ensure that:
|
||||
Before the end of life date, please ensure that:
|
||||
|
||||
- when reading SRV records, you use only the `name` outside of the data map and ignore `service`, `proto` and `name` within the data map if they exist; and
|
||||
- when writing SRV records, you set the `name` outside of the data map and **do not set** `service`, `proto` or `name` within the data map.
|
||||
- when reading SRV records, you use only the `name` outside of the data map and ignore `service`, `proto` and `name` within the data map if they exist; and
|
||||
- when writing SRV records, you set the `name` outside of the data map and **do not set** `service`, `proto` or `name` within the data map.
|
||||
|
||||
After the end of life date, the API will stop producing the `service`, `proto` and `name` data fields, and if any of them are received from a client, an error will be returned.
|
||||
After the end of life date, the API will stop producing the `service`, `proto` and `name` data fields, and if any of them are received from a client, an error will be returned.
|
||||
|
||||
This deprecation does not affect other SRV data fields not mentioned above (`priority`, `weight`, `port`, `target`) or data fields for any other record type other than SRV.
|
||||
This deprecation does not affect other SRV data fields not mentioned above (`priority`, `weight`, `port`, `target`) or data fields for any other record type other than SRV.
|
||||
|
||||
Modified API:
|
||||
Modified API:
|
||||
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `GET /zones/:zone_id/dns_records`
|
||||
- `POST /zones/:zone_id/dns_records`
|
||||
- `GET /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PATCH /zones/:zone_id/dns_records/:dns_record_id`
|
||||
- `PUT /zones/:zone_id/dns_records/:dns_record_id`
|
||||
|
||||
- publish_date: '2024-03-31'
|
||||
title: "Privacy Pass API Removal"
|
||||
description: |-
|
||||
Deprecation date: March 31, 2024
|
||||
- publish_date: "2024-03-31"
|
||||
title: "Privacy Pass API Removal"
|
||||
description: |-
|
||||
Deprecation date: March 31, 2024
|
||||
|
||||
In 2017, Cloudflare [announced support](https://blog.cloudflare.com/cloudflare-supports-privacy-pass/) for Privacy Pass, a recent protocol to let users prove their identity across multiple sites anonymously without enabling tracking. The initial use case was to provide untraceable tokens to sites to vouch for users who might otherwise have been presented with a CAPTCHA challenge. In the time since this release, Privacy Pass has evolved both at the [IETF](https://datatracker.ietf.org/wg/privacypass/documents/) and within Cloudflare. The version announced in 2017 is now considered legacy, and these legacy Privacy Pass tokens are no longer supported as an alternative to Cloudflare challenges. As has been discussed on our blog [The end road for CAPTCHA](https://blog.cloudflare.com/end-cloudflare-captcha/), Cloudflare uses a variety of signals to infer if incoming traffic is likely automated. The (legacy) Privacy Pass zone setting is no longer meaningful to Cloudflare customers as Cloudflare now operates [CAPTCHA free](https://blog.cloudflare.com/turnstile-ga/), and supports the latest [Privacy Pass draft](https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/).
|
||||
|
||||
In September 2023, support for legacy Privacy Pass tokens as an alternative to Cloudflare Managed Challenge was removed. By the end of March 2024, the current public-facing API will be removed as well.
|
||||
In 2017, Cloudflare [announced support](https://blog.cloudflare.com/cloudflare-supports-privacy-pass/) for Privacy Pass, a recent protocol to let users prove their identity across multiple sites anonymously without enabling tracking. The initial use case was to provide untraceable tokens to sites to vouch for users who might otherwise have been presented with a CAPTCHA challenge. In the time since this release, Privacy Pass has evolved both at the [IETF](https://datatracker.ietf.org/wg/privacypass/documents/) and within Cloudflare. The version announced in 2017 is now considered legacy, and these legacy Privacy Pass tokens are no longer supported as an alternative to Cloudflare challenges. As has been discussed on our blog [The end road for CAPTCHA](https://blog.cloudflare.com/end-cloudflare-captcha/), Cloudflare uses a variety of signals to infer if incoming traffic is likely automated. The (legacy) Privacy Pass zone setting is no longer meaningful to Cloudflare customers as Cloudflare now operates [CAPTCHA free](https://blog.cloudflare.com/turnstile-ga/), and supports the latest [Privacy Pass draft](https://blog.cloudflare.com/eliminating-captchas-on-iphones-and-macs-using-new-standard/).
|
||||
|
||||
Deprecated API:
|
||||
In September 2023, support for legacy Privacy Pass tokens as an alternative to Cloudflare Managed Challenge was removed. By the end of March 2024, the current public-facing API will be removed as well.
|
||||
|
||||
- `GET zones/:zone_identifier/settings/privacy_pass`
|
||||
- `POST zones/:zone_identifier/settings/privacy_pass`
|
||||
Deprecated API:
|
||||
|
||||
- publish_date: '2024-02-04'
|
||||
title: "Argo Tunnel"
|
||||
description: |-
|
||||
Deprecation date: February 4, 2024
|
||||
- `GET zones/:zone_identifier/settings/privacy_pass`
|
||||
- `POST zones/:zone_identifier/settings/privacy_pass`
|
||||
|
||||
This endpoint and its related APIs are deprecated in favor of the Cloudflare Tunnels equivalent APIs.
|
||||
- publish_date: "2024-02-04"
|
||||
title: "Argo Tunnel"
|
||||
description: |-
|
||||
Deprecation date: February 4, 2024
|
||||
|
||||
Deprecated API:
|
||||
This endpoint and its related APIs are deprecated in favor of the Cloudflare Tunnels equivalent APIs.
|
||||
|
||||
- `GET accounts/:account_identifier/tunnels`
|
||||
- `POST accounts/:account_identifier/tunnels`
|
||||
- `GET accounts/:account_identifier/tunnels/:tunnel_id`
|
||||
- `DELETE accounts/:account_identifier/tunnels/:tunnel_id`
|
||||
Deprecated API:
|
||||
|
||||
Replacement:
|
||||
Cloudflare Tunnel API
|
||||
- `GET accounts/:account_identifier/tunnels`
|
||||
- `POST accounts/:account_identifier/tunnels`
|
||||
- `GET accounts/:account_identifier/tunnels/:tunnel_id`
|
||||
- `DELETE accounts/:account_identifier/tunnels/:tunnel_id`
|
||||
|
||||
- publish_date: '2023-07-01'
|
||||
title: "ChaCha20 TLS Cipher Removal"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2023
|
||||
Replacement:
|
||||
Cloudflare Tunnel API
|
||||
|
||||
Back in 2016, Cloudflare [introduced support](https://blog.cloudflare.com/it-takes-two-to-chacha-poly/) for `ChaCha20-Poly1305` cipher suites for TLS 1.2. At the time, we introduced two variants of these new suites, the "standard" suites as defined by the IETF RFC 7905, and "draft" suites that followed an earlier draft of said specification. The draft suites were added for compatibility with some older Android devices that at the time did not yet support the proper `ChaCha20-Poly1305` standard versions. This was in 2016, and in the meantime the standard `ChaCha20-Poly1305` cipher suites have gained much wider adoption, to the point were traffic using the old suites has dropped significantly. Due to the current low usage and the non-standard nature of these cipher suites, we are now deprecating their support on the Cloudflare network.
|
||||
- publish_date: "2023-07-01"
|
||||
title: "ChaCha20 TLS Cipher Removal"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2023
|
||||
|
||||
This should not affect customer zones in any way, as clients that might currently use these cipher suites will be able to fallback to different ones. In addition, unlike the standard variants, these legacy cipher suites are not exposed directly through our API (e.g. through the TLS cipher suites preferences endpoint), and their deprecation will not affect customer configurations in any way.
|
||||
Back in 2016, Cloudflare [introduced support](https://blog.cloudflare.com/it-takes-two-to-chacha-poly/) for `ChaCha20-Poly1305` cipher suites for TLS 1.2. At the time, we introduced two variants of these new suites, the "standard" suites as defined by the IETF RFC 7905, and "draft" suites that followed an earlier draft of said specification. The draft suites were added for compatibility with some older Android devices that at the time did not yet support the proper `ChaCha20-Poly1305` standard versions. This was in 2016, and in the meantime the standard `ChaCha20-Poly1305` cipher suites have gained much wider adoption, to the point were traffic using the old suites has dropped significantly. Due to the current low usage and the non-standard nature of these cipher suites, we are now deprecating their support on the Cloudflare network.
|
||||
|
||||
As of July 1st, 2023, the ChaCha20-Poly1305 ciphers have been deprecated and are deemed End of Life by Cloudflare. If you have clients that currently rely on these ciphers, it is strongly recommended to upgrade them to newer, more secure ciphers. Be aware that these deprecated ciphers will be completely removed in the first quarter of 2024, and requests using them will start to fail. Take proactive measures to ensure a smooth transition and maintain the security of your systems.
|
||||
This should not affect customer zones in any way, as clients that might currently use these cipher suites will be able to fallback to different ones. In addition, unlike the standard variants, these legacy cipher suites are not exposed directly through our API (e.g. through the TLS cipher suites preferences endpoint), and their deprecation will not affect customer configurations in any way.
|
||||
|
||||
- publish_date: '2023-07-01'
|
||||
title: "Transfer-Encoding and Content-Length headers"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2023
|
||||
As of July 1st, 2023, the ChaCha20-Poly1305 ciphers have been deprecated and are deemed End of Life by Cloudflare. If you have clients that currently rely on these ciphers, it is strongly recommended to upgrade them to newer, more secure ciphers. Be aware that these deprecated ciphers will be completely removed in the first quarter of 2024, and requests using them will start to fail. Take proactive measures to ensure a smooth transition and maintain the security of your systems.
|
||||
|
||||
Previously, RFC 2616 allowed the use of `Transfer-Encoding` and `Content-Length` HTTP headers in the same request. RFC 7230 supersedes RFC 2616 and prohibits the use of `Transfer-Encoding` and `Content-Length` headers in the same request because they can cause HTTP request smuggling vulnerabilities.
|
||||
- publish_date: "2023-07-01"
|
||||
title: "Transfer-Encoding and Content-Length headers"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2023
|
||||
|
||||
Starting on July 1st, 2023, Cloudflare will decline requests with both `Transfer-Encoding` and `Content-Length` HTTP headers.
|
||||
Previously, RFC 2616 allowed the use of `Transfer-Encoding` and `Content-Length` HTTP headers in the same request. RFC 7230 supersedes RFC 2616 and prohibits the use of `Transfer-Encoding` and `Content-Length` headers in the same request because they can cause HTTP request smuggling vulnerabilities.
|
||||
|
||||
- publish_date: '2023-06-06'
|
||||
title: "Account Billing Profile, User Billing Profile, and User Billing History"
|
||||
description: |-
|
||||
Deprecation date: June 6, 2023
|
||||
Starting on July 1st, 2023, Cloudflare will decline requests with both `Transfer-Encoding` and `Content-Length` HTTP headers.
|
||||
|
||||
There is no API replacement for these endpoints. As an alternative, please log in to your Cloudflare account to view your:
|
||||
- publish_date: "2023-06-06"
|
||||
title: "Account Billing Profile, User Billing Profile, and User Billing History"
|
||||
description: |-
|
||||
Deprecation date: June 6, 2023
|
||||
|
||||
- [Invoices & Billing Email](https://dash.cloudflare.com/?to=/:account/billing)
|
||||
- [Billing subscriptions](https://dash.cloudflare.com/?to=/:account/billing/subscriptions)
|
||||
- [Billing profile payment info](https://dash.cloudflare.com/?to=/:account/billing/payment-info)
|
||||
There is no API replacement for these endpoints. As an alternative, please log in to your Cloudflare account to view your:
|
||||
|
||||
Deprecated API:
|
||||
- [Invoices & Billing Email](https://dash.cloudflare.com/?to=/:account/billing)
|
||||
- [Billing subscriptions](https://dash.cloudflare.com/?to=/:account/billing/subscriptions)
|
||||
- [Billing profile payment info](https://dash.cloudflare.com/?to=/:account/billing/payment-info)
|
||||
|
||||
- `GET accounts/{account_identifier}/billing/profile`
|
||||
- `GET user/billing/profile`
|
||||
- `GET user/billing/history`
|
||||
Deprecated API:
|
||||
|
||||
- publish_date: '2023-04-03'
|
||||
title: "Load Balancing - notification_email"
|
||||
description: |-
|
||||
Deprecation date: April 3, 2023
|
||||
- `GET accounts/{account_identifier}/billing/profile`
|
||||
- `GET user/billing/profile`
|
||||
- `GET user/billing/history`
|
||||
|
||||
This field is deprecated and has been moved to [Cloudflare centralized notification service](/notifications/).
|
||||
- publish_date: "2023-04-03"
|
||||
title: "Load Balancing - notification_email"
|
||||
description: |-
|
||||
Deprecation date: April 3, 2023
|
||||
|
||||
`notification_email` is the email address to send health status notifications to. This can be an individual mailbox or a mailing list. Multiple emails can be supplied as a comma delimited list.
|
||||
This field is deprecated and has been moved to [Cloudflare centralized notification service](/notifications/).
|
||||
|
||||
- publish_date: '2023-03-19'
|
||||
title: "Access Bookmark applications"
|
||||
description: |-
|
||||
Deprecation date: March 19, 2023
|
||||
`notification_email` is the email address to send health status notifications to. This can be an individual mailbox or a mailing list. Multiple emails can be supplied as a comma delimited list.
|
||||
|
||||
This endpoint is deprecated in favor of using a specialized Access Application App Type API.
|
||||
- publish_date: "2023-03-19"
|
||||
title: "Access Bookmark applications"
|
||||
description: |-
|
||||
Deprecation date: March 19, 2023
|
||||
|
||||
Deprecated API:
|
||||
This endpoint is deprecated in favor of using a specialized Access Application App Type API.
|
||||
|
||||
- `GET accounts/:identifier/access/bookmarks`
|
||||
- `GET accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `POST accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `PUT accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `DELETE accounts/:identifier/access/bookmarks/:uuid`
|
||||
Deprecated API:
|
||||
|
||||
Replacement:
|
||||
Access applications app type API
|
||||
- `GET accounts/:identifier/access/bookmarks`
|
||||
- `GET accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `POST accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `PUT accounts/:identifier/access/bookmarks/:uuid`
|
||||
- `DELETE accounts/:identifier/access/bookmarks/:uuid`
|
||||
|
||||
- publish_date: '2022-10-11'
|
||||
title: "Page Shield"
|
||||
description: |-
|
||||
Deprecation date: October 11, 2022
|
||||
Replacement:
|
||||
Access applications app type API
|
||||
|
||||
Replace `script_monitor` in Page Shield API routes with `page_shield`.
|
||||
- publish_date: "2022-10-11"
|
||||
title: "Page Shield"
|
||||
description: |-
|
||||
Deprecation date: October 11, 2022
|
||||
|
||||
- publish_date: '2022-07-01'
|
||||
title: "Cloudflare Images - Create authenticated direct upload URL v1"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2022
|
||||
Replace `script_monitor` in Page Shield API routes with `page_shield`.
|
||||
|
||||
This endpoint is deprecated in favor of using v2, which allows you to control metadata, define an access policy, and get the image ID.
|
||||
- publish_date: "2022-07-01"
|
||||
title: "Cloudflare Images - Create authenticated direct upload URL v1"
|
||||
description: |-
|
||||
Deprecation date: July 1, 2022
|
||||
|
||||
Deprecated API:
|
||||
`POST accounts/:account_identifier/images/v1/direct_upload`
|
||||
This endpoint is deprecated in favor of using v2, which allows you to control metadata, define an access policy, and get the image ID.
|
||||
|
||||
Replacement:
|
||||
`POST accounts/:account_identifier/images/v2/direct_upload`
|
||||
Deprecated API:
|
||||
`POST accounts/:account_identifier/images/v1/direct_upload`
|
||||
|
||||
- publish_date: '2021-03-01'
|
||||
title: "Zone Analytics API"
|
||||
description: |-
|
||||
Deprecation date: March 1, 2021
|
||||
Replacement:
|
||||
`POST accounts/:account_identifier/images/v2/direct_upload`
|
||||
|
||||
This API is deprecated in favor of the [GraphQL Analytics API](/analytics/graphql-api/), which provides equivalent data and more features, including the ability to select only the metrics that you need. For more information, refer to the [Zone analytics to GraphQL analytics migration guide](/analytics/graphql-api/migration-guides/zone-analytics/).
|
||||
- publish_date: "2021-03-01"
|
||||
title: "Zone Analytics API"
|
||||
description: |-
|
||||
Deprecation date: March 1, 2021
|
||||
|
||||
Deprecated API:
|
||||
This API is deprecated in favor of the [GraphQL Analytics API](/analytics/graphql-api/), which provides equivalent data and more features, including the ability to select only the metrics that you need. For more information, refer to the [Zone analytics to GraphQL analytics migration guide](/analytics/graphql-api/migration-guides/zone-analytics/).
|
||||
|
||||
- `GET zones/:zone_identifier/analytics/dashboard`
|
||||
- `GET zones/:zone_identifier/analytics/colos`
|
||||
Deprecated API:
|
||||
|
||||
Replacement:
|
||||
GraphQL Analytics API
|
||||
- `GET zones/:zone_identifier/analytics/dashboard`
|
||||
- `GET zones/:zone_identifier/analytics/colos`
|
||||
|
||||
- publish_date: '2020-04-02'
|
||||
title: "Organizations"
|
||||
description: |-
|
||||
Deprecation date: April 2, 2020
|
||||
Replacement:
|
||||
GraphQL Analytics API
|
||||
|
||||
This endpoint and its related APIs are deprecated in favor of the `/accounts` equivalent API, which has a broader range of features and is backwards compatible with the `/organizations` API.
|
||||
|
||||
Deprecated API:
|
||||
- publish_date: "2020-04-02"
|
||||
title: "Organizations"
|
||||
description: |-
|
||||
Deprecation date: April 2, 2020
|
||||
|
||||
- `GET organizations/:identifier`
|
||||
- `PATCH organizations/:identifier`
|
||||
- `GET organizations/:organization_identifier/invites`
|
||||
- `POST organizations/:organization_identifier/invites`
|
||||
- `GET organizations/:organization_identifier/invites/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/invites/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/invites/:identifier`
|
||||
- `GET organizations/:organization_identifier/members`
|
||||
- `GET organizations/:organization_identifier/members/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/members/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/members/:identifier`
|
||||
- `GET organizations/:organization_identifier/roles`
|
||||
- `GET organizations/:organization_identifier/roles/:identifier`
|
||||
- `GET organizations/:organization_identifier/audit_logs`
|
||||
- `GET organizations/:organization_identifier/railguns`
|
||||
- `POST organizations/:organization_identifier/railguns`
|
||||
- `GET organizations/:organization_identifier/railguns/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/railguns/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/railguns/:identifier`
|
||||
- `GET organizations/:organization_identifier/railguns/:identifier/zones`
|
||||
This endpoint and its related APIs are deprecated in favor of the `/accounts` equivalent API, which has a broader range of features and is backwards compatible with the `/organizations` API.
|
||||
|
||||
Replacement:
|
||||
Accounts API
|
||||
Deprecated API:
|
||||
|
||||
- `GET organizations/:identifier`
|
||||
- `PATCH organizations/:identifier`
|
||||
- `GET organizations/:organization_identifier/invites`
|
||||
- `POST organizations/:organization_identifier/invites`
|
||||
- `GET organizations/:organization_identifier/invites/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/invites/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/invites/:identifier`
|
||||
- `GET organizations/:organization_identifier/members`
|
||||
- `GET organizations/:organization_identifier/members/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/members/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/members/:identifier`
|
||||
- `GET organizations/:organization_identifier/roles`
|
||||
- `GET organizations/:organization_identifier/roles/:identifier`
|
||||
- `GET organizations/:organization_identifier/audit_logs`
|
||||
- `GET organizations/:organization_identifier/railguns`
|
||||
- `POST organizations/:organization_identifier/railguns`
|
||||
- `GET organizations/:organization_identifier/railguns/:identifier`
|
||||
- `PATCH organizations/:organization_identifier/railguns/:identifier`
|
||||
- `DELETE organizations/:organization_identifier/railguns/:identifier`
|
||||
- `GET organizations/:organization_identifier/railguns/:identifier/zones`
|
||||
|
||||
Replacement:
|
||||
Accounts API
|
||||
|
|
|
|||
|
|
@ -5,33 +5,32 @@ productLink: "/api-shield/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: "2024-08-28"
|
||||
title: Increased capacity for Endpoint Management and Schema Validation
|
||||
description: |-
|
||||
Endpoint Management and Schema Validation now support up to 10,000 saved and validated API endpoints.
|
||||
|
||||
- publish_date: '2024-08-28'
|
||||
title: Increased capacity for Endpoint Management and Schema Validation
|
||||
description: |-
|
||||
Endpoint Management and Schema Validation now support up to 10,000 saved and validated API endpoints.
|
||||
- publish_date: "2024-07-08"
|
||||
title: API Discovery's hostname variables
|
||||
description: |-
|
||||
Customers can now see when [API Discovery](/api-shield/security/api-discovery/) groups similar subdomains with the same methods and paths, making it easy to discover and manage APIs that share many vanity domains or subdomains.
|
||||
|
||||
- publish_date: '2024-07-08'
|
||||
title: API Discovery's hostname variables
|
||||
description: |-
|
||||
Customers can now see when [API Discovery](/api-shield/security/api-discovery/) groups similar subdomains with the same methods and paths, making it easy to discover and manage APIs that share many vanity domains or subdomains.
|
||||
- publish_date: "2024-07-02"
|
||||
title: Route API requests using API Routing
|
||||
description: |-
|
||||
Customers can now route requests to different back-end services through [API Routing](/api-shield/management-and-monitoring/api-routing/), creating a unified front for their APIs distributed across otherwise disparate systems.
|
||||
|
||||
- publish_date: '2024-07-02'
|
||||
title: Route API requests using API Routing
|
||||
description: |-
|
||||
Customers can now route requests to different back-end services through [API Routing](/api-shield/management-and-monitoring/api-routing/), creating a unified front for their APIs distributed across otherwise disparate systems.
|
||||
- publish_date: "2024-05-13"
|
||||
title: Use JWT claims in Advanced Rate Limiting, Transform Rules, and as session IDs
|
||||
description: |-
|
||||
Customers can now use the fields inside [JSON Web Tokens (known as claims)](/api-shield/security/jwt-validation/transform-rules/#enhance-transform-rules-with-jwt-claims) as [session identifiers in API Shield](/api-shield/get-started/#session-identifiers), to count values in [Advanced Rate Limiting](/waf/rate-limiting-rules/), and to send on useful information in [Transform Rules](/rules/transform/#transform-rules).
|
||||
|
||||
- publish_date: '2024-05-13'
|
||||
title: Use JWT claims in Advanced Rate Limiting, Transform Rules, and as session IDs
|
||||
description: |-
|
||||
Customers can now use the fields inside [JSON Web Tokens (known as claims)](/api-shield/security/jwt-validation/transform-rules/#enhance-transform-rules-with-jwt-claims) as [session identifiers in API Shield](/api-shield/get-started/#session-identifiers), to count values in [Advanced Rate Limiting](/waf/rate-limiting-rules/), and to send on useful information in [Transform Rules](/rules/transform/#transform-rules).
|
||||
- publish_date: "2024-04-30"
|
||||
title: Build Sequence Mitigation rules via the Cloudflare dashboard
|
||||
description: |-
|
||||
Customers can now build [Sequence Mitigation](/api-shield/security/sequence-mitigation/) rules with a new user interface inside the API Shield section of the [Cloudflare dashboard](https://dash.cloudflare.com/).
|
||||
|
||||
- publish_date: '2024-04-30'
|
||||
title: Build Sequence Mitigation rules via the Cloudflare dashboard
|
||||
description: |-
|
||||
Customers can now build [Sequence Mitigation](/api-shield/security/sequence-mitigation/) rules with a new user interface inside the API Shield section of the [Cloudflare dashboard](https://dash.cloudflare.com/).
|
||||
|
||||
- publish_date: '2024-02-23'
|
||||
title: Endpoint Management supports hostname variables
|
||||
description: |-
|
||||
Customers can now save endpoints in [Endpoint Management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.
|
||||
- publish_date: "2024-02-23"
|
||||
title: Endpoint Management supports hostname variables
|
||||
description: |-
|
||||
Customers can now save endpoints in [Endpoint Management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.
|
||||
|
|
|
|||
|
|
@ -5,51 +5,51 @@ productLink: "/web-analytics/"
|
|||
productArea: Application performance
|
||||
productAreaLink: /fundamentals/reference/changelog/performance/
|
||||
entries:
|
||||
- publish_date: '2024-06-11'
|
||||
description: Enhanced to include reporting of Server-Timing headers.
|
||||
- publish_date: "2024-06-11"
|
||||
description: Enhanced to include reporting of Server-Timing headers.
|
||||
|
||||
- publish_date: '2024-05-22'
|
||||
description: Introducing new metric fields, transferSize and decodedBodySize are included.
|
||||
- publish_date: "2024-05-22"
|
||||
description: Introducing new metric fields, transferSize and decodedBodySize are included.
|
||||
|
||||
- publish_date: '2024-04-17'
|
||||
description: Introducing new metric fields, deliveryType (dt) and navigationType (nt) are included.
|
||||
- publish_date: "2024-04-17"
|
||||
description: Introducing new metric fields, deliveryType (dt) and navigationType (nt) are included.
|
||||
|
||||
- publish_date: '2023-10-18'
|
||||
description: Manages A/B testing tags.
|
||||
- publish_date: "2023-10-18"
|
||||
description: Manages A/B testing tags.
|
||||
|
||||
- publish_date: '2023-07-25'
|
||||
description: Fixed ETag format in the response header.
|
||||
- publish_date: "2023-07-25"
|
||||
description: Fixed ETag format in the response header.
|
||||
|
||||
- publish_date: '2023-07-13'
|
||||
description: Fixed the issue that was causing an illegal invocation error.
|
||||
- publish_date: "2023-07-13"
|
||||
description: Fixed the issue that was causing an illegal invocation error.
|
||||
|
||||
- publish_date: '2023-04-19'
|
||||
description: Reports additional LCP diagnostic information using web-vitals library's attribution build.
|
||||
- publish_date: "2023-04-19"
|
||||
description: Reports additional LCP diagnostic information using web-vitals library's attribution build.
|
||||
|
||||
- publish_date: '2023-04-06'
|
||||
description: Updated webpack configuration to output code in ECMAScript 3 (ES3) format.
|
||||
- publish_date: "2023-04-06"
|
||||
description: Updated webpack configuration to output code in ECMAScript 3 (ES3) format.
|
||||
|
||||
- publish_date: '2023-03-23'
|
||||
description: Updated Google's web-vitals library (version 3.1.1) and removed experimental `server-timing` header.
|
||||
- publish_date: "2023-03-23"
|
||||
description: Updated Google's web-vitals library (version 3.1.1) and removed experimental `server-timing` header.
|
||||
|
||||
- publish_date: '2022-10-17'
|
||||
description: Updated to report new metrics such as time to first byte (TTFB), interaction to next paint (INP), and first contentful paint (FCP). Additionally, it reports `navigator.webdriver`, `server-timing` header (experimental), and protocol info (`nextHopProtocol`).
|
||||
- publish_date: "2022-10-17"
|
||||
description: Updated to report new metrics such as time to first byte (TTFB), interaction to next paint (INP), and first contentful paint (FCP). Additionally, it reports `navigator.webdriver`, `server-timing` header (experimental), and protocol info (`nextHopProtocol`).
|
||||
|
||||
- publish_date: '2021-12-14'
|
||||
description: Improved site filtering.
|
||||
- publish_date: "2021-12-14"
|
||||
description: Improved site filtering.
|
||||
|
||||
- publish_date: '2021-11-16'
|
||||
description: |-
|
||||
When using the automatic installation feature of the JavaScript Beacon (available only to customers proxied through Cloudflare - also known as orange-clouded customers),
|
||||
[Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) is now enabled by default. SRI is a security feature that enables browsers to
|
||||
verify that resources they fetch are delivered without unexpected manipulation.
|
||||
- publish_date: "2021-11-16"
|
||||
description: |-
|
||||
When using the automatic installation feature of the JavaScript Beacon (available only to customers proxied through Cloudflare - also known as orange-clouded customers),
|
||||
[Subresource Integrity (SRI)](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity) is now enabled by default. SRI is a security feature that enables browsers to
|
||||
verify that resources they fetch are delivered without unexpected manipulation.
|
||||
|
||||
- publish_date: '2021-09-01'
|
||||
description: Improved to report debugging information for Core Web Vitals.
|
||||
- publish_date: "2021-09-01"
|
||||
description: Improved to report debugging information for Core Web Vitals.
|
||||
|
||||
- publish_date: '2021-05-28'
|
||||
description: |-
|
||||
`startsWith` function replaced with `indexOf` function, which prevents rendering if multiple beacon scripts are loaded.
|
||||
- publish_date: "2021-05-28"
|
||||
description: |-
|
||||
`startsWith` function replaced with `indexOf` function, which prevents rendering if multiple beacon scripts are loaded.
|
||||
|
||||
- publish_date: '2021-05-12'
|
||||
description: Reporting endpoint changed from `/cdn-cgi/beacon/performance` to `/cdn-cgi/rum` (for Browser Insights only).
|
||||
- publish_date: "2021-05-12"
|
||||
description: Reporting endpoint changed from `/cdn-cgi/beacon/performance` to `/cdn-cgi/rum` (for Browser Insights only).
|
||||
|
|
|
|||
|
|
@ -5,8 +5,7 @@ productLink: "/bots/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
|
||||
- publish_date: '2024-08-19'
|
||||
title: AI bots is now a managed rule
|
||||
description: |-
|
||||
[AI bots protection](/bots/concepts/bot/#ai-bots) has been upgraded from a custom rule to a managed rule.
|
||||
- publish_date: "2024-08-19"
|
||||
title: AI bots is now a managed rule
|
||||
description: |-
|
||||
[AI bots protection](/bots/concepts/bot/#ai-bots) has been upgraded from a custom rule to a managed rule.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/cloudflare-one/policies/browser-isolation/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-03-21'
|
||||
title: Removed third-party cookie dependencies
|
||||
description: |-
|
||||
Removed dependency on third-party cookies in the isolated browser, fixing an issue that previously caused intermittent disruptions for users maintaining multi-site, cross-tab sessions in the isolated browser.
|
||||
- publish_date: "2024-03-21"
|
||||
title: Removed third-party cookie dependencies
|
||||
description: |-
|
||||
Removed dependency on third-party cookies in the isolated browser, fixing an issue that previously caused intermittent disruptions for users maintaining multi-site, cross-tab sessions in the isolated browser.
|
||||
|
|
|
|||
|
|
@ -5,15 +5,15 @@ productLink: "/browser-rendering/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-08-08'
|
||||
title: Update puppeteer to 21.1.0
|
||||
description: |-
|
||||
* Rebased the fork on the original implementation up till version 21.1.0
|
||||
- publish_date: '2024-04-02'
|
||||
title: Browser Rendering Available for everyone
|
||||
description: |-
|
||||
* Browser Rendering is now out of beta and available to all customers with Workers Paid Plan. Analytics and logs are available in Cloudflare's dashboard, under "Worker & Pages".
|
||||
- publish_date: '2023-05-19'
|
||||
title: Browser Rendering Beta
|
||||
description: |-
|
||||
* Beta Launch
|
||||
- publish_date: "2024-08-08"
|
||||
title: Update puppeteer to 21.1.0
|
||||
description: |-
|
||||
* Rebased the fork on the original implementation up till version 21.1.0
|
||||
- publish_date: "2024-04-02"
|
||||
title: Browser Rendering Available for everyone
|
||||
description: |-
|
||||
* Browser Rendering is now out of beta and available to all customers with Workers Paid Plan. Analytics and logs are available in Cloudflare's dashboard, under "Worker & Pages".
|
||||
- publish_date: "2023-05-19"
|
||||
title: Browser Rendering Beta
|
||||
description: |-
|
||||
* Beta Launch
|
||||
|
|
|
|||
|
|
@ -5,15 +5,15 @@ productLink: "/cloudflare-one/applications/scan-apps/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-06-03'
|
||||
title: Atlassian Bitbucket integration
|
||||
description: |-
|
||||
Customers can now scan their Bitbucket Cloud workspaces for a variety of contextualized security issues such as source code exposure, admin misconfigurations, and more.
|
||||
- publish_date: '2024-05-23'
|
||||
title: Data-at-rest DLP for Box and Dropbox
|
||||
description: |-
|
||||
You can now scan your [Box](/cloudflare-one/applications/scan-apps/casb-integrations/box/#data-loss-prevention-optional) and [Dropbox](/cloudflare-one/applications/scan-apps/casb-integrations/dropbox/#data-loss-prevention-optional) files for DLP matches.
|
||||
- publish_date: '2024-04-16'
|
||||
title: Export CASB findings to CSV
|
||||
description: |-
|
||||
You can now export all top-level CASB findings or every instance of your findings to CSV.
|
||||
- publish_date: "2024-06-03"
|
||||
title: Atlassian Bitbucket integration
|
||||
description: |-
|
||||
Customers can now scan their Bitbucket Cloud workspaces for a variety of contextualized security issues such as source code exposure, admin misconfigurations, and more.
|
||||
- publish_date: "2024-05-23"
|
||||
title: Data-at-rest DLP for Box and Dropbox
|
||||
description: |-
|
||||
You can now scan your [Box](/cloudflare-one/applications/scan-apps/casb-integrations/box/#data-loss-prevention-optional) and [Dropbox](/cloudflare-one/applications/scan-apps/casb-integrations/dropbox/#data-loss-prevention-optional) files for DLP matches.
|
||||
- publish_date: "2024-04-16"
|
||||
title: Export CASB findings to CSV
|
||||
description: |-
|
||||
You can now export all top-level CASB findings or every instance of your findings to CSV.
|
||||
|
|
|
|||
|
|
@ -7,110 +7,110 @@ topLevelLink: "/ddos-protection/change-log/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-04-19'
|
||||
scheduled_date: '2024-04-29'
|
||||
scheduled: true
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/scheduled-changes/'
|
||||
- publish_date: '2024-04-19'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-04-19/'
|
||||
- publish_date: '2024-04-16'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-04-16-emergency/'
|
||||
- publish_date: '2024-04-04'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-04-04-emergency/'
|
||||
- publish_date: '2024-04-02'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-04-02/'
|
||||
- publish_date: '2024-02-26'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-26-emergency/'
|
||||
- publish_date: '2024-02-19'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-19/'
|
||||
- publish_date: '2024-02-12'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-12/'
|
||||
- publish_date: '2024-02-08'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-08-emergency/'
|
||||
- publish_date: '2024-02-06'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-06-emergency/'
|
||||
- publish_date: '2024-02-05'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-02-05-emergency/'
|
||||
- publish_date: '2024-01-26'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-01-26-emergency/'
|
||||
- publish_date: '2024-01-25'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-01-25/'
|
||||
- publish_date: '2024-01-23'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-01-23/'
|
||||
- publish_date: '2024-01-05'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2024-01-05/'
|
||||
- publish_date: '2023-12-19'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-12-19-emergency/'
|
||||
- publish_date: '2023-12-14'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-12-14-emergency/'
|
||||
- publish_date: '2023-12-08'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-12-08-emergency/'
|
||||
- publish_date: '2023-11-29'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-11-29/'
|
||||
- publish_date: '2023-11-22'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-11-22/'
|
||||
- publish_date: '2023-11-13'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-11-13-emergency/'
|
||||
- publish_date: '2023-11-10'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-11-10-emergency/'
|
||||
- publish_date: '2023-10-19'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-10-19/'
|
||||
- publish_date: '2023-10-11'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-10-11/'
|
||||
- publish_date: '2023-10-09'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-10-09-emergency/'
|
||||
- publish_date: '2023-09-24'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-09-24-emergency/'
|
||||
- publish_date: '2023-09-21'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-09-21-emergency/'
|
||||
- publish_date: '2023-09-05'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-09-05-emergency/'
|
||||
- publish_date: '2023-08-30'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-30-emergency/'
|
||||
- publish_date: '2023-08-29'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-29-emergency/'
|
||||
- publish_date: '2023-08-25'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-25-emergency/'
|
||||
- publish_date: '2023-08-16'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-16-emergency/'
|
||||
- publish_date: '2023-08-14'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-14/'
|
||||
- publish_date: '2023-08-11'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-08-11-emergency/'
|
||||
- publish_date: '2023-07-31'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/http/2023-07-31/'
|
||||
- publish_date: "2024-04-19"
|
||||
scheduled_date: "2024-04-29"
|
||||
scheduled: true
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/scheduled-changes/"
|
||||
- publish_date: "2024-04-19"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-04-19/"
|
||||
- publish_date: "2024-04-16"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-04-16-emergency/"
|
||||
- publish_date: "2024-04-04"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-04-04-emergency/"
|
||||
- publish_date: "2024-04-02"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-04-02/"
|
||||
- publish_date: "2024-02-26"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-26-emergency/"
|
||||
- publish_date: "2024-02-19"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-19/"
|
||||
- publish_date: "2024-02-12"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-12/"
|
||||
- publish_date: "2024-02-08"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-08-emergency/"
|
||||
- publish_date: "2024-02-06"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-06-emergency/"
|
||||
- publish_date: "2024-02-05"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-02-05-emergency/"
|
||||
- publish_date: "2024-01-26"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-01-26-emergency/"
|
||||
- publish_date: "2024-01-25"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-01-25/"
|
||||
- publish_date: "2024-01-23"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-01-23/"
|
||||
- publish_date: "2024-01-05"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2024-01-05/"
|
||||
- publish_date: "2023-12-19"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-12-19-emergency/"
|
||||
- publish_date: "2023-12-14"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-12-14-emergency/"
|
||||
- publish_date: "2023-12-08"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-12-08-emergency/"
|
||||
- publish_date: "2023-11-29"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-11-29/"
|
||||
- publish_date: "2023-11-22"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-11-22/"
|
||||
- publish_date: "2023-11-13"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-11-13-emergency/"
|
||||
- publish_date: "2023-11-10"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-11-10-emergency/"
|
||||
- publish_date: "2023-10-19"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-10-19/"
|
||||
- publish_date: "2023-10-11"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-10-11/"
|
||||
- publish_date: "2023-10-09"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-10-09-emergency/"
|
||||
- publish_date: "2023-09-24"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-09-24-emergency/"
|
||||
- publish_date: "2023-09-21"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-09-21-emergency/"
|
||||
- publish_date: "2023-09-05"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-09-05-emergency/"
|
||||
- publish_date: "2023-08-30"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-30-emergency/"
|
||||
- publish_date: "2023-08-29"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-29-emergency/"
|
||||
- publish_date: "2023-08-25"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-25-emergency/"
|
||||
- publish_date: "2023-08-16"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-16-emergency/"
|
||||
- publish_date: "2023-08-14"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-14/"
|
||||
- publish_date: "2023-08-11"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-08-11-emergency/"
|
||||
- publish_date: "2023-07-31"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/http/2023-07-31/"
|
||||
|
|
|
|||
|
|
@ -7,15 +7,15 @@ topLevelLink: "/ddos-protection/change-log/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-03-12'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/network/2024-03-12/'
|
||||
- publish_date: '2023-07-31'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/network/2023-07-31/'
|
||||
- publish_date: '2023-04-17'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/network/2023-04-17/'
|
||||
- publish_date: '2022-12-02'
|
||||
individual_page: true
|
||||
link: '/ddos-protection/change-log/network/2022-12-02/'
|
||||
- publish_date: "2024-03-12"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/network/2024-03-12/"
|
||||
- publish_date: "2023-07-31"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/network/2023-07-31/"
|
||||
- publish_date: "2023-04-17"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/network/2023-04-17/"
|
||||
- publish_date: "2022-12-02"
|
||||
individual_page: true
|
||||
link: "/ddos-protection/change-log/network/2022-12-02/"
|
||||
|
|
|
|||
|
|
@ -7,14 +7,14 @@ topLevelLink: "/ddos-protection/change-log/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-06-03'
|
||||
title: DDoS alerts now available for EU CMB customers
|
||||
description: |-
|
||||
[DDoS alerts](/ddos-protection/reference/alerts/) are now available for EU Customer Metadata Boundary (CMB) customers. This includes all DDoS alert type (Standard and Advanced) for both HTTP DDoS attacks and L3/4 DDoS attacks.
|
||||
- publish_date: "2024-06-03"
|
||||
title: DDoS alerts now available for EU CMB customers
|
||||
description: |-
|
||||
[DDoS alerts](/ddos-protection/reference/alerts/) are now available for EU Customer Metadata Boundary (CMB) customers. This includes all DDoS alert type (Standard and Advanced) for both HTTP DDoS attacks and L3/4 DDoS attacks.
|
||||
|
||||
- publish_date: '2024-04-17'
|
||||
title: Network Analytics now supported for EU CMB customers
|
||||
description: |-
|
||||
The Network Analytics dashboard is available to customers that have opted in to the EU [Customer Metadata Boundary](/data-localization/metadata-boundary/) (CMB) solution. This also includes Network Analytics Logs (Logpush) and GraphQL API.
|
||||
- publish_date: "2024-04-17"
|
||||
title: Network Analytics now supported for EU CMB customers
|
||||
description: |-
|
||||
The Network Analytics dashboard is available to customers that have opted in to the EU [Customer Metadata Boundary](/data-localization/metadata-boundary/) (CMB) solution. This also includes Network Analytics Logs (Logpush) and GraphQL API.
|
||||
|
||||
API users can ensure they are routed properly by directing their API requests at `eu.api.cloudflare.com`.
|
||||
API users can ensure they are routed properly by directing their API requests at `eu.api.cloudflare.com`.
|
||||
|
|
|
|||
|
|
@ -5,14 +5,14 @@ productLink: "/cloudflare-one/insights/dex/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-05-20'
|
||||
title: Last seen ISP
|
||||
description: |-
|
||||
Admins can view the last ISP seen for a device by going to **My Team** > **Devices**. Requires setting up a [traceroute test](/cloudflare-one/insights/dex/tests/traceroute/).
|
||||
- publish_date: '2024-05-13'
|
||||
title: DEX alerts
|
||||
description: |-
|
||||
Admins can now set [DEX alerts](/cloudflare-one/insights/dex/notifications/) using [Cloudflare Notifications](/notifications/). Three new DEX alert types:
|
||||
- Device connectivity anomaly
|
||||
- Test latency
|
||||
- Test low availability
|
||||
- publish_date: "2024-05-20"
|
||||
title: Last seen ISP
|
||||
description: |-
|
||||
Admins can view the last ISP seen for a device by going to **My Team** > **Devices**. Requires setting up a [traceroute test](/cloudflare-one/insights/dex/tests/traceroute/).
|
||||
- publish_date: "2024-05-13"
|
||||
title: DEX alerts
|
||||
description: |-
|
||||
Admins can now set [DEX alerts](/cloudflare-one/insights/dex/notifications/) using [Cloudflare Notifications](/notifications/). Three new DEX alert types:
|
||||
- Device connectivity anomaly
|
||||
- Test latency
|
||||
- Test low availability
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/durable-objects/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-06-24'
|
||||
- publish_date: "2024-06-24"
|
||||
description: |-
|
||||
[Exceptions](/durable-objects/best-practices/error-handling) thrown from Durable Object internal operations and tunneled to the caller may now be populated with a `.retryable: true` property if the exception was likely due to a transient failure, or populated with an `.overloaded: true` property if the exception was due to [overload](/durable-objects/observability/troubleshooting/#durable-object-is-overloaded).
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/cloudflare-one/email-security/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-08-06'
|
||||
title: Email Security is live
|
||||
description: |-
|
||||
Email Security is now live under Zero Trust.
|
||||
- publish_date: "2024-08-06"
|
||||
title: Email Security is live
|
||||
description: |-
|
||||
Email Security is now live under Zero Trust.
|
||||
|
|
|
|||
|
|
@ -5,12 +5,11 @@ productLink: "/kv/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: "2024-08-08"
|
||||
title: New KV Analytics API
|
||||
description: |-
|
||||
|
||||
- publish_date: "2024-08-08"
|
||||
title: New KV Analytics API
|
||||
description: |-
|
||||
Workers KV now has a new [metrics dashboard](/kv/observability/metrics-analytics/#view-metrics-in-the-dashboard) and [analytics API](/kv/observability/metrics-analytics/#query-via-the-graphql-api) that leverages the [GraphQL Analytics API](/analytics/graphql-api/) used by many other Cloudflare products. The new analytics API provides per-account and per-namespace metrics for both operations and storage, including latency metrics for read and write operations to Workers KV.
|
||||
|
||||
Workers KV now has a new [metrics dashboard](/kv/observability/metrics-analytics/#view-metrics-in-the-dashboard) and [analytics API](/kv/observability/metrics-analytics/#query-via-the-graphql-api) that leverages the [GraphQL Analytics API](/analytics/graphql-api/) used by many other Cloudflare products. The new analytics API provides per-account and per-namespace metrics for both operations and storage, including latency metrics for read and write operations to Workers KV.
|
||||
|
||||
The legacy Workers KV [analytics REST API](/api/operations/workers-kv-request-analytics-query-request-analytics) will be turned off as of January 31st, 2025.
|
||||
Developers using this API will receive a series of email notifications prior to the shutdown of the legacy API.
|
||||
The legacy Workers KV [analytics REST API](/api/operations/workers-kv-request-analytics-query-request-analytics) will be turned off as of January 31st, 2025.
|
||||
Developers using this API will receive a series of email notifications prior to the shutdown of the legacy API.
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@ productLink: "/magic-firewall/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-08-16'
|
||||
title: Magic Firewall Analytics Rule Log Enhancement
|
||||
description: |-
|
||||
Customers who create a rule in a disabled mode will see the rule as **Log (rule disabled)**.
|
||||
- publish_date: '2024-09-12'
|
||||
title: New UI improvements
|
||||
description: |-
|
||||
The dashboard now displays the order number of custom rules, and improved drag and drop functionality. You can also preview rules on a side panel without leaving the current page.
|
||||
- publish_date: "2024-08-16"
|
||||
title: Magic Firewall Analytics Rule Log Enhancement
|
||||
description: |-
|
||||
Customers who create a rule in a disabled mode will see the rule as **Log (rule disabled)**.
|
||||
- publish_date: "2024-09-12"
|
||||
title: New UI improvements
|
||||
description: |-
|
||||
The dashboard now displays the order number of custom rules, and improved drag and drop functionality. You can also preview rules on a side panel without leaving the current page.
|
||||
|
|
|
|||
|
|
@ -5,23 +5,23 @@ productLink: "/magic-wan/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-07-17'
|
||||
title: Updates to High Availability on the Magic WAN Connector
|
||||
description: |-
|
||||
The High Availability feature on Magic WAN Connector now supports additional failover conditions, DHCP lease syncing, and staggered upgrades.
|
||||
- publish_date: '2024-06-23'
|
||||
title: ICMP support for traffic sourced from private IPs
|
||||
description: |-
|
||||
Magic WAN will now support ICMP traffic sourced from private IPs going to the Internet via Gateway.
|
||||
- publish_date: '2024-06-05'
|
||||
title: Application based prioritization
|
||||
description: |-
|
||||
The Magic WAN Connector can now prioritize traffic on a per-application basis.
|
||||
- publish_date: '2024-05-31'
|
||||
title: WARP virtual IP addresses
|
||||
description: |-
|
||||
Customers using Gateway to filter traffic to Magic WAN destinations will now see traffic from Cloudflare egressing with WARP virtual IP addresses (CGNAT range), rather than public Cloudflare IP addresses. This simplifies configuration and improves visibility for customers.
|
||||
- publish_date: '2024-01-23'
|
||||
title: Network segmentation
|
||||
description: |-
|
||||
You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
|
||||
- publish_date: "2024-07-17"
|
||||
title: Updates to High Availability on the Magic WAN Connector
|
||||
description: |-
|
||||
The High Availability feature on Magic WAN Connector now supports additional failover conditions, DHCP lease syncing, and staggered upgrades.
|
||||
- publish_date: "2024-06-23"
|
||||
title: ICMP support for traffic sourced from private IPs
|
||||
description: |-
|
||||
Magic WAN will now support ICMP traffic sourced from private IPs going to the Internet via Gateway.
|
||||
- publish_date: "2024-06-05"
|
||||
title: Application based prioritization
|
||||
description: |-
|
||||
The Magic WAN Connector can now prioritize traffic on a per-application basis.
|
||||
- publish_date: "2024-05-31"
|
||||
title: WARP virtual IP addresses
|
||||
description: |-
|
||||
Customers using Gateway to filter traffic to Magic WAN destinations will now see traffic from Cloudflare egressing with WARP virtual IP addresses (CGNAT range), rather than public Cloudflare IP addresses. This simplifies configuration and improves visibility for customers.
|
||||
- publish_date: "2024-01-23"
|
||||
title: Network segmentation
|
||||
description: |-
|
||||
You can define policies in your Connector to either allow traffic to flow between your LANs without it leaving your local premises or to forward it via the Cloudflare network where you can add additional security features.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/network-interconnect/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-09-02'
|
||||
title: Interconnect portal displays all available locations in a list
|
||||
description: |-
|
||||
Customers can now see all available Express CNI locations when searching for a Cloudflare site in the Interconnects interface.
|
||||
- publish_date: "2024-09-02"
|
||||
title: Interconnect portal displays all available locations in a list
|
||||
description: |-
|
||||
Customers can now see all available Express CNI locations when searching for a Cloudflare site in the Interconnects interface.
|
||||
|
|
|
|||
|
|
@ -5,27 +5,22 @@ productLink: "/notifications/"
|
|||
productArea: Core platform
|
||||
productAreaLink: /fundamentals/reference/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2023-10-06'
|
||||
|
||||
description: |-
|
||||
* Added **Traffic Anomalies Alerts** to notify customers when traffic to their domain has an unexpected spike or drop.
|
||||
- publish_date: '2023-09-28'
|
||||
|
||||
description: |-
|
||||
* Added **[Incident Alerts](https://blog.cloudflare.com/incident-alerts/)**.
|
||||
- publish_date: '2023-08-23'
|
||||
|
||||
description: |-
|
||||
* Added **Logo Match Alert**.
|
||||
- publish_date: '2023-04-19'
|
||||
|
||||
description: |-
|
||||
* Added **Maintenance Notification Alerts**.
|
||||
- publish_date: '2023-03-13'
|
||||
|
||||
description: |-
|
||||
* Added **Pages Alerts**.
|
||||
- publish_date: '2023-03-02'
|
||||
|
||||
description: |-
|
||||
* Added **Brand Protection Alerts**.
|
||||
- publish_date: "2023-10-06"
|
||||
|
||||
description: |-
|
||||
* Added **Traffic Anomalies Alerts** to notify customers when traffic to their domain has an unexpected spike or drop.
|
||||
- publish_date: "2023-09-28"
|
||||
description: |-
|
||||
* Added **[Incident Alerts](https://blog.cloudflare.com/incident-alerts/)**.
|
||||
- publish_date: "2023-08-23"
|
||||
description: |-
|
||||
* Added **Logo Match Alert**.
|
||||
- publish_date: "2023-04-19"
|
||||
description: |-
|
||||
* Added **Maintenance Notification Alerts**.
|
||||
- publish_date: "2023-03-13"
|
||||
description: |-
|
||||
* Added **Pages Alerts**.
|
||||
- publish_date: "2023-03-02"
|
||||
description: |-
|
||||
* Added **Brand Protection Alerts**.
|
||||
|
|
|
|||
|
|
@ -5,28 +5,27 @@ productLink: "/page-shield/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: "2024-06-18"
|
||||
title: Cookie Monitor now available
|
||||
description: |-
|
||||
Page Shield now captures HTTP cookies set and used by your web application. The [list of detected cookies](/page-shield/detection/monitor-connections-scripts/) in available in the Cloudflare dashboard or via API.
|
||||
|
||||
- publish_date: '2024-06-18'
|
||||
title: Cookie Monitor now available
|
||||
description: |-
|
||||
Page Shield now captures HTTP cookies set and used by your web application. The [list of detected cookies](/page-shield/detection/monitor-connections-scripts/) in available in the Cloudflare dashboard or via API.
|
||||
- publish_date: "2024-06-14"
|
||||
title: Added filter operators for scripts and connections
|
||||
description: |-
|
||||
You can now filter scripts and connections in the Cloudflare dashboard using the `does not contain` operator. Pages associated with scripts and connections can be filtered by `includes`, `starts with`, and `ends with`.
|
||||
|
||||
- publish_date: '2024-06-14'
|
||||
title: Added filter operators for scripts and connections
|
||||
description: |-
|
||||
You can now filter scripts and connections in the Cloudflare dashboard using the `does not contain` operator. Pages associated with scripts and connections can be filtered by `includes`, `starts with`, and `ends with`.
|
||||
- publish_date: "2024-04-26"
|
||||
title: Suggestions for the default directive
|
||||
description: |-
|
||||
When creating a policy in the dashboard, default directive aggregates suggestions of monitored scripts and connections data, enabling defining default directive easier.
|
||||
|
||||
- publish_date: '2024-04-26'
|
||||
title: Suggestions for the default directive
|
||||
description: |-
|
||||
When creating a policy in the dashboard, default directive aggregates suggestions of monitored scripts and connections data, enabling defining default directive easier.
|
||||
- publish_date: "2024-04-04"
|
||||
title: Individual threat intelligence categories
|
||||
description: |-
|
||||
Instead of aggregating categories of URL and domain data from threat intelligence, they are now listed per type.
|
||||
|
||||
- publish_date: '2024-04-04'
|
||||
title: Individual threat intelligence categories
|
||||
description: |-
|
||||
Instead of aggregating categories of URL and domain data from threat intelligence, they are now listed per type.
|
||||
|
||||
- publish_date: '2024-03-21'
|
||||
title: Increase allowed length per policy
|
||||
description: |-
|
||||
Now each policy supports up to 6,000 characters.
|
||||
- publish_date: "2024-03-21"
|
||||
title: Increase allowed length per policy
|
||||
description: |-
|
||||
Now each policy supports up to 6,000 characters.
|
||||
|
|
|
|||
|
|
@ -5,130 +5,130 @@ productLink: "/pages/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2023-09-13'
|
||||
title: Support for D1's new storage subsystem and build error message improvements
|
||||
description: |-
|
||||
* Added support for D1's [new storage subsystem](https://blog.cloudflare.com/d1-turning-it-up-to-11/). All Git builds and deployments done with Wrangler v3.5.0 and up can use the new subsystem.
|
||||
* Builds which fail due to exceeding the [build time limit](https://developers.cloudflare.com/pages/platform/limits/#builds) will return a proper error message indicating so rather than `Internal error`.
|
||||
* New and improved error messages for other build failures
|
||||
- publish_date: '2023-08-23'
|
||||
title: Commit message limit increase
|
||||
description: |-
|
||||
* Commit messages can now be up to 384 characters before being trimmed.
|
||||
- publish_date: '2023-08-01'
|
||||
title: Support for newer TLDs
|
||||
description: |-
|
||||
* Support newer TLDs such as `.party` and `.music`.
|
||||
- publish_date: '2023-07-11'
|
||||
title: V2 build system enabled by default
|
||||
description: |-
|
||||
- V2 build system is now default for all new projects.
|
||||
- publish_date: '2023-07-10'
|
||||
title: Sped up project creation
|
||||
description: |-
|
||||
* Sped up project creation.
|
||||
- publish_date: '2023-05-19'
|
||||
title: Build error message improvement
|
||||
description: |-
|
||||
* Builds which fail due to Out of memory (OOM) will return a proper error message indicating so rather than `Internal error`.
|
||||
- publish_date: '2023-05-17'
|
||||
title: V2 build system beta
|
||||
description: |-
|
||||
* The V2 build system is now available in open beta. Enable the V2 build system by going to your Pages project in the Cloudflare dashboard and selecting **Settings** > [**Build & deployments**](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/settings/builds-deployments) > **Build system version**.
|
||||
- publish_date: '2023-05-16'
|
||||
title: Support for Smart Placement
|
||||
description: |-
|
||||
* [Smart placement](/workers/configuration/smart-placement/) can now be enabled for Pages within your Pages Project by going to **Settings** > [**Functions**](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/settings/functions).
|
||||
- publish_date: '2023-03-23'
|
||||
title: Git projects can now see files uploaded
|
||||
description: |-
|
||||
* Files uploaded are now visible for Git projects, you can view them in the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/files).
|
||||
- publish_date: '2023-03-20'
|
||||
title: Notifications for Pages are now available
|
||||
description: |-
|
||||
* Notifications for Pages events are now available in the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/notifications). Events supported include:
|
||||
* Deployment started.
|
||||
* Deployment succeeded.
|
||||
* Deployment failed.
|
||||
- publish_date: '2023-02-14'
|
||||
title: Analytics Engine now available in Functions
|
||||
description: |-
|
||||
- Added support for [Analytics Engine](/analytics/analytics-engine/)
|
||||
in Functions.
|
||||
- publish_date: '2023-01-05'
|
||||
title: Queues now available in Functions
|
||||
description: |-
|
||||
- Added support for [Queues](/queues/) producer in Functions.
|
||||
- publish_date: '2022-12-15'
|
||||
title: API messaging update
|
||||
description: Updated all API messaging to be more helpful.
|
||||
- publish_date: '2022-12-01'
|
||||
title: Ability to delete aliased deployments
|
||||
description: |-
|
||||
- Aliased deployments can now be deleted. If using the API, you will need to add the query parameter `force=true`.
|
||||
- publish_date: '2022-11-19'
|
||||
title: Deep linking to a Pages deployment
|
||||
description: |-
|
||||
- You can now deep-link to a Pages deployment in the dashboard with `:pages-deployment`. An example would be `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment`.
|
||||
- publish_date: '2022-11-17'
|
||||
title: Functions GA and other updates
|
||||
description: |-
|
||||
- Pages functions are now GA. For more information, refer to the [blog post](https://blog.cloudflare.com/pages-function-goes-ga/).
|
||||
- We also made the following updates to Functions:
|
||||
- [Functions metrics](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/analytics/production) are now available in the dashboard.
|
||||
- [Functions billing](/pages/functions/pricing/) is now available.
|
||||
- The [Unbound usage model](/workers/platform/limits/#response-limits) is now available for Functions.
|
||||
- [Secrets](/pages/functions/bindings/#secrets) are now available.
|
||||
- Functions tailing is now available via the [dashboard](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions) or with Wrangler (`wrangler pages deployment tail`).
|
||||
- publish_date: '2022-11-15'
|
||||
title: Service bindings now available in Functions
|
||||
description: |-
|
||||
- Service bindings are now available in Functions. For more details,
|
||||
refer to the [docs](/pages/functions/bindings/#service-bindings).
|
||||
- publish_date: '2022-11-03'
|
||||
title: Ansi color codes in build logs
|
||||
description: Build log now supports ansi color codes.
|
||||
- publish_date: '2022-10-05'
|
||||
title: Deep linking to a Pages project
|
||||
description: |-
|
||||
- You can now deep-link to a Pages project in the dashboard with `:pages-project`. An example would be `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project`.
|
||||
- publish_date: '2022-09-12'
|
||||
title: Increased domain limits
|
||||
description: |-
|
||||
Previously, all plans had a maximum of 10 [custom domains](/pages/configuration/custom-domains/) per project.
|
||||
- publish_date: "2023-09-13"
|
||||
title: Support for D1's new storage subsystem and build error message improvements
|
||||
description: |-
|
||||
* Added support for D1's [new storage subsystem](https://blog.cloudflare.com/d1-turning-it-up-to-11/). All Git builds and deployments done with Wrangler v3.5.0 and up can use the new subsystem.
|
||||
* Builds which fail due to exceeding the [build time limit](https://developers.cloudflare.com/pages/platform/limits/#builds) will return a proper error message indicating so rather than `Internal error`.
|
||||
* New and improved error messages for other build failures
|
||||
- publish_date: "2023-08-23"
|
||||
title: Commit message limit increase
|
||||
description: |-
|
||||
* Commit messages can now be up to 384 characters before being trimmed.
|
||||
- publish_date: "2023-08-01"
|
||||
title: Support for newer TLDs
|
||||
description: |-
|
||||
* Support newer TLDs such as `.party` and `.music`.
|
||||
- publish_date: "2023-07-11"
|
||||
title: V2 build system enabled by default
|
||||
description: |-
|
||||
- V2 build system is now default for all new projects.
|
||||
- publish_date: "2023-07-10"
|
||||
title: Sped up project creation
|
||||
description: |-
|
||||
* Sped up project creation.
|
||||
- publish_date: "2023-05-19"
|
||||
title: Build error message improvement
|
||||
description: |-
|
||||
* Builds which fail due to Out of memory (OOM) will return a proper error message indicating so rather than `Internal error`.
|
||||
- publish_date: "2023-05-17"
|
||||
title: V2 build system beta
|
||||
description: |-
|
||||
* The V2 build system is now available in open beta. Enable the V2 build system by going to your Pages project in the Cloudflare dashboard and selecting **Settings** > [**Build & deployments**](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/settings/builds-deployments) > **Build system version**.
|
||||
- publish_date: "2023-05-16"
|
||||
title: Support for Smart Placement
|
||||
description: |-
|
||||
* [Smart placement](/workers/configuration/smart-placement/) can now be enabled for Pages within your Pages Project by going to **Settings** > [**Functions**](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/settings/functions).
|
||||
- publish_date: "2023-03-23"
|
||||
title: Git projects can now see files uploaded
|
||||
description: |-
|
||||
* Files uploaded are now visible for Git projects, you can view them in the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/files).
|
||||
- publish_date: "2023-03-20"
|
||||
title: Notifications for Pages are now available
|
||||
description: |-
|
||||
* Notifications for Pages events are now available in the [Cloudflare dashboard](https://dash.cloudflare.com?to=/:account/notifications). Events supported include:
|
||||
* Deployment started.
|
||||
* Deployment succeeded.
|
||||
* Deployment failed.
|
||||
- publish_date: "2023-02-14"
|
||||
title: Analytics Engine now available in Functions
|
||||
description: |-
|
||||
- Added support for [Analytics Engine](/analytics/analytics-engine/)
|
||||
in Functions.
|
||||
- publish_date: "2023-01-05"
|
||||
title: Queues now available in Functions
|
||||
description: |-
|
||||
- Added support for [Queues](/queues/) producer in Functions.
|
||||
- publish_date: "2022-12-15"
|
||||
title: API messaging update
|
||||
description: Updated all API messaging to be more helpful.
|
||||
- publish_date: "2022-12-01"
|
||||
title: Ability to delete aliased deployments
|
||||
description: |-
|
||||
- Aliased deployments can now be deleted. If using the API, you will need to add the query parameter `force=true`.
|
||||
- publish_date: "2022-11-19"
|
||||
title: Deep linking to a Pages deployment
|
||||
description: |-
|
||||
- You can now deep-link to a Pages deployment in the dashboard with `:pages-deployment`. An example would be `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment`.
|
||||
- publish_date: "2022-11-17"
|
||||
title: Functions GA and other updates
|
||||
description: |-
|
||||
- Pages functions are now GA. For more information, refer to the [blog post](https://blog.cloudflare.com/pages-function-goes-ga/).
|
||||
- We also made the following updates to Functions:
|
||||
- [Functions metrics](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/analytics/production) are now available in the dashboard.
|
||||
- [Functions billing](/pages/functions/pricing/) is now available.
|
||||
- The [Unbound usage model](/workers/platform/limits/#response-limits) is now available for Functions.
|
||||
- [Secrets](/pages/functions/bindings/#secrets) are now available.
|
||||
- Functions tailing is now available via the [dashboard](https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment/functions) or with Wrangler (`wrangler pages deployment tail`).
|
||||
- publish_date: "2022-11-15"
|
||||
title: Service bindings now available in Functions
|
||||
description: |-
|
||||
- Service bindings are now available in Functions. For more details,
|
||||
refer to the [docs](/pages/functions/bindings/#service-bindings).
|
||||
- publish_date: "2022-11-03"
|
||||
title: Ansi color codes in build logs
|
||||
description: Build log now supports ansi color codes.
|
||||
- publish_date: "2022-10-05"
|
||||
title: Deep linking to a Pages project
|
||||
description: |-
|
||||
- You can now deep-link to a Pages project in the dashboard with `:pages-project`. An example would be `https://dash.cloudflare.com?to=/:account/pages/view/:pages-project`.
|
||||
- publish_date: "2022-09-12"
|
||||
title: Increased domain limits
|
||||
description: |-
|
||||
Previously, all plans had a maximum of 10 [custom domains](/pages/configuration/custom-domains/) per project.
|
||||
|
||||
Now, the limits are:
|
||||
Now, the limits are:
|
||||
|
||||
- **Free**: 100 custom domains.
|
||||
- **Pro**: 250 custom domains.
|
||||
- **Business** and **Enterprise**: 500 custom domains.
|
||||
- publish_date: '2022-09-08'
|
||||
title: Support for _routes.json
|
||||
description: |-
|
||||
- Pages now offers support for `_routes.json`. For more details, refer
|
||||
to the [documentation](/pages/functions/routing/#functions-invocation-routes).
|
||||
- publish_date: '2022-08-25'
|
||||
title: Increased build log expiration time
|
||||
description: Build log expiration time increased from 2 weeks to 1 year.
|
||||
- publish_date: '2022-08-08'
|
||||
title: New bindings supported
|
||||
description: |-
|
||||
- R2 and D1 [bindings](/pages/functions/bindings/) are now supported.
|
||||
- publish_date: '2022-07-05'
|
||||
title: Added support for .dev.vars in wrangler pages
|
||||
description: |-
|
||||
Pages now supports `.dev.vars` in `wrangler pages`, which allows you to use use environmental variables during your local development without chaining `--env`s.
|
||||
- **Free**: 100 custom domains.
|
||||
- **Pro**: 250 custom domains.
|
||||
- **Business** and **Enterprise**: 500 custom domains.
|
||||
- publish_date: "2022-09-08"
|
||||
title: Support for _routes.json
|
||||
description: |-
|
||||
- Pages now offers support for `_routes.json`. For more details, refer
|
||||
to the [documentation](/pages/functions/routing/#functions-invocation-routes).
|
||||
- publish_date: "2022-08-25"
|
||||
title: Increased build log expiration time
|
||||
description: Build log expiration time increased from 2 weeks to 1 year.
|
||||
- publish_date: "2022-08-08"
|
||||
title: New bindings supported
|
||||
description: |-
|
||||
- R2 and D1 [bindings](/pages/functions/bindings/) are now supported.
|
||||
- publish_date: "2022-07-05"
|
||||
title: Added support for .dev.vars in wrangler pages
|
||||
description: |-
|
||||
Pages now supports `.dev.vars` in `wrangler pages`, which allows you to use use environmental variables during your local development without chaining `--env`s.
|
||||
|
||||
This functionality requires Wrangler v2.0.16 or higher.
|
||||
- publish_date: '2022-06-13'
|
||||
title: Added deltas to wrangler pages publish
|
||||
description: |-
|
||||
Pages has added deltas to `wrangler pages publish`.
|
||||
This functionality requires Wrangler v2.0.16 or higher.
|
||||
- publish_date: "2022-06-13"
|
||||
title: Added deltas to wrangler pages publish
|
||||
description: |-
|
||||
Pages has added deltas to `wrangler pages publish`.
|
||||
|
||||
We now keep track of the files that make up each deployment and intelligently only upload the files that we have not seen. This means that similar subsequent deployments should only need to upload a minority of files and this will hopefully make uploads even faster.
|
||||
We now keep track of the files that make up each deployment and intelligently only upload the files that we have not seen. This means that similar subsequent deployments should only need to upload a minority of files and this will hopefully make uploads even faster.
|
||||
|
||||
This functionality requires Wrangler v2.0.11 or higher.
|
||||
- publish_date: '2022-06-08'
|
||||
title: Added branch alias to PR comments
|
||||
description: |-
|
||||
- PR comments for Pages previews now include the branch alias.
|
||||
This functionality requires Wrangler v2.0.11 or higher.
|
||||
- publish_date: "2022-06-08"
|
||||
title: Added branch alias to PR comments
|
||||
description: |-
|
||||
- PR comments for Pages previews now include the branch alias.
|
||||
|
|
|
|||
|
|
@ -5,74 +5,78 @@ productLink: "/queues/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-03-26'
|
||||
title: Delay messages published to a queue
|
||||
description: |-
|
||||
Messages published to a queue and/or marked for retry from a queue consumer can now be explicitly delayed. Delaying messages allows you to defer tasks until later, and/or respond to backpressure when consuming from a queue.
|
||||
- publish_date: "2024-03-26"
|
||||
title: Delay messages published to a queue
|
||||
description: |-
|
||||
Messages published to a queue and/or marked for retry from a queue consumer can now be explicitly delayed. Delaying messages allows you to defer tasks until later, and/or respond to backpressure when consuming from a queue.
|
||||
|
||||
Refer to [Batching and Retries](/queues/configuration/batching-retries/) to learn how to delay messages written to a queue.
|
||||
- publish_date: '2024-03-25'
|
||||
title: Support for pull-based consumers
|
||||
description: |-
|
||||
Queues now supports [pull-based consumers](/queues/configuration/pull-consumers/). A pull-based consumer allows you to pull from a queue over HTTP from any environment and/or programming language outside of Cloudflare Workers. A pull-based consumer can be useful when your message consumption rate is limited by upstream infrastructure or long-running tasks.
|
||||
Refer to [Batching and Retries](/queues/configuration/batching-retries/) to learn how to delay messages written to a queue.
|
||||
- publish_date: "2024-03-25"
|
||||
title: Support for pull-based consumers
|
||||
description: |-
|
||||
Queues now supports [pull-based consumers](/queues/configuration/pull-consumers/). A pull-based consumer allows you to pull from a queue over HTTP from any environment and/or programming language outside of Cloudflare Workers. A pull-based consumer can be useful when your message consumption rate is limited by upstream infrastructure or long-running tasks.
|
||||
|
||||
Review the [documentation on pull-based consumers](/queues/configuration/pull-consumers/) to configure HTTP-based pull.
|
||||
- publish_date: '2024-03-18'
|
||||
title: Default content type now set to JSON
|
||||
description: |-
|
||||
The default [content type](/queues/configuration/javascript-apis/#queuescontenttype) for messages published to a queue is now `json`, which improves compatibility with the upcoming pull-based queues.
|
||||
Review the [documentation on pull-based consumers](/queues/configuration/pull-consumers/) to configure HTTP-based pull.
|
||||
- publish_date: "2024-03-18"
|
||||
title: Default content type now set to JSON
|
||||
description: |-
|
||||
The default [content type](/queues/configuration/javascript-apis/#queuescontenttype) for messages published to a queue is now `json`, which improves compatibility with the upcoming pull-based queues.
|
||||
|
||||
Any Workers created on or after the [compatibility date](/workers/configuration/compatibility-dates/#queues-send-messages-in-json-format) of `2024-03-18`, or that explicitly set the `queues_json_messages` compatibility flag, will use the new default behaviour. Existing Workers with a compatibility date prior will continue to use `v8` as the default content type for published messages.
|
||||
- publish_date: '2024-02-24'
|
||||
title: Explicit retries no longer impact consumer concurrency/scaling.
|
||||
description: |-
|
||||
Calling `retry()` or `retryAll()` on a message or message batch will no longer have an impact on how Queues scales [consumer concurrency](/queues/configuration/consumer-concurrency/).
|
||||
Any Workers created on or after the [compatibility date](/workers/configuration/compatibility-dates/#queues-send-messages-in-json-format) of `2024-03-18`, or that explicitly set the `queues_json_messages` compatibility flag, will use the new default behaviour. Existing Workers with a compatibility date prior will continue to use `v8` as the default content type for published messages.
|
||||
- publish_date: "2024-02-24"
|
||||
title: Explicit retries no longer impact consumer concurrency/scaling.
|
||||
description: |-
|
||||
Calling `retry()` or `retryAll()` on a message or message batch will no longer have an impact on how Queues scales [consumer concurrency](/queues/configuration/consumer-concurrency/).
|
||||
|
||||
Previously, using [explicit retries](/queues/configuration/batching-retries/#explicit-acknowledgement-and-retries) via `retry()` or `retryAll()` would count as an error and could result in Queues scaling down the number of concurrent consumers.
|
||||
- publish_date: '2023-10-07'
|
||||
title: More queues per account - up to 10,000
|
||||
description: |-
|
||||
Developers building on Queues can now create up to 10,000 queues per account, enabling easier per-user, per-job and sharding use-cases.
|
||||
Previously, using [explicit retries](/queues/configuration/batching-retries/#explicit-acknowledgement-and-retries) via `retry()` or `retryAll()` would count as an error and could result in Queues scaling down the number of concurrent consumers.
|
||||
- publish_date: "2023-10-07"
|
||||
title: More queues per account - up to 10,000
|
||||
description: |-
|
||||
Developers building on Queues can now create up to 10,000 queues per account, enabling easier per-user, per-job and sharding use-cases.
|
||||
|
||||
Refer to [Limits](/queues/platform/limits) to learn more about Queues' current limits.
|
||||
- publish_date: '2023-10-05'
|
||||
title: Higher consumer concurrency limits
|
||||
description: |-
|
||||
[Queue consumers](/queues/configuration/consumer-concurrency/) can now scale to 20 concurrent invocations (per queue), up from 10. This allows you to scale out and process higher throughput queues more quickly.
|
||||
Refer to [Limits](/queues/platform/limits) to learn more about Queues' current limits.
|
||||
- publish_date: "2023-10-05"
|
||||
title: Higher consumer concurrency limits
|
||||
description: |-
|
||||
[Queue consumers](/queues/configuration/consumer-concurrency/) can now scale to 20 concurrent invocations (per queue), up from 10. This allows you to scale out and process higher throughput queues more quickly.
|
||||
|
||||
Queues with [no explicit limit specified](/queues/configuration/consumer-concurrency/#limit-concurrency) will automatically scale to the new maximum.
|
||||
Queues with [no explicit limit specified](/queues/configuration/consumer-concurrency/#limit-concurrency) will automatically scale to the new maximum.
|
||||
|
||||
This limit will continue to grow during the Queues beta.
|
||||
- publish_date: '2023-03-28'
|
||||
title: Consumer concurrency (enabled)
|
||||
description: Queue consumers will now [automatically scale up](/queues/configuration/consumer-concurrency/)
|
||||
based on the number of messages being written to the queue. To control or limit
|
||||
concurrency, you can explicitly define a [`max_concurrency`](/queues/configuration/configure-queues/#consumer)
|
||||
for your consumer.
|
||||
- publish_date: '2023-03-15'
|
||||
title: Consumer concurrency (upcoming)
|
||||
description: |-
|
||||
Queue consumers will soon automatically scale up concurrently as a queues' backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.
|
||||
This limit will continue to grow during the Queues beta.
|
||||
- publish_date: "2023-03-28"
|
||||
title: Consumer concurrency (enabled)
|
||||
description:
|
||||
Queue consumers will now [automatically scale up](/queues/configuration/consumer-concurrency/)
|
||||
based on the number of messages being written to the queue. To control or limit
|
||||
concurrency, you can explicitly define a [`max_concurrency`](/queues/configuration/configure-queues/#consumer)
|
||||
for your consumer.
|
||||
- publish_date: "2023-03-15"
|
||||
title: Consumer concurrency (upcoming)
|
||||
description: |-
|
||||
Queue consumers will soon automatically scale up concurrently as a queues' backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.
|
||||
|
||||
**To opt-out, or to configure a fixed maximum concurrency**, set `max_concurrency = 1` in your `wrangler.toml` file or via [the queues dashboard](https://dash.cloudflare.com/?to=/:account/queues).
|
||||
**To opt-out, or to configure a fixed maximum concurrency**, set `max_concurrency = 1` in your `wrangler.toml` file or via [the queues dashboard](https://dash.cloudflare.com/?to=/:account/queues).
|
||||
|
||||
**To opt-in, you do not need to take any action**: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the [consumer concurrency](/queues/configuration/consumer-concurrency/) documentation.
|
||||
- publish_date: '2023-03-02'
|
||||
title: Explicit acknowledgement (new feature)
|
||||
description: |-
|
||||
You can now [acknowledge individual messages with a batch](/queues/configuration/batching-retries/#explicit-acknowledgement-and-retries) by calling `.ack()` on a message.
|
||||
**To opt-in, you do not need to take any action**: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the [consumer concurrency](/queues/configuration/consumer-concurrency/) documentation.
|
||||
- publish_date: "2023-03-02"
|
||||
title: Explicit acknowledgement (new feature)
|
||||
description: |-
|
||||
You can now [acknowledge individual messages with a batch](/queues/configuration/batching-retries/#explicit-acknowledgement-and-retries) by calling `.ack()` on a message.
|
||||
|
||||
This allows you to mark a message as delivered as you process it within a batch, and avoids the entire batch from being redelivered if your consumer throws an error during batch processing. This can be particularly useful when you are calling external APIs, writing messages to a database, or otherwise performing non-idempotent actions on individual messages within a batch.
|
||||
- publish_date: '2023-03-01'
|
||||
title: Higher per-queue throughput
|
||||
description: The per-queue throughput limit has now been [raised to 400 messages
|
||||
per second](/queues/platform/limits/).
|
||||
- publish_date: '2022-12-12'
|
||||
title: Increased per-account limits
|
||||
description: Queues now allows developers to create up to 100 queues per account,
|
||||
up from the initial beta limit of 10 per account. This limit will continue to
|
||||
increase over time.
|
||||
- publish_date: '2022-12-13'
|
||||
title: sendBatch support
|
||||
description: The JavaScript API for Queue producers now includes a `sendBatch` method
|
||||
which supports sending up to 100 messages at a time.
|
||||
This allows you to mark a message as delivered as you process it within a batch, and avoids the entire batch from being redelivered if your consumer throws an error during batch processing. This can be particularly useful when you are calling external APIs, writing messages to a database, or otherwise performing non-idempotent actions on individual messages within a batch.
|
||||
- publish_date: "2023-03-01"
|
||||
title: Higher per-queue throughput
|
||||
description:
|
||||
The per-queue throughput limit has now been [raised to 400 messages
|
||||
per second](/queues/platform/limits/).
|
||||
- publish_date: "2022-12-12"
|
||||
title: Increased per-account limits
|
||||
description:
|
||||
Queues now allows developers to create up to 100 queues per account,
|
||||
up from the initial beta limit of 10 per account. This limit will continue to
|
||||
increase over time.
|
||||
- publish_date: "2022-12-13"
|
||||
title: sendBatch support
|
||||
description:
|
||||
The JavaScript API for Queue producers now includes a `sendBatch` method
|
||||
which supports sending up to 100 messages at a time.
|
||||
|
|
|
|||
|
|
@ -5,269 +5,269 @@ productLink: "/r2/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-06-07'
|
||||
description: |-
|
||||
- publish_date: "2024-06-07"
|
||||
description: |-
|
||||
- Fixed an issue that prevented Sippy from copying over objects from S3 buckets with SSE set up.
|
||||
- publish_date: '2024-06-06'
|
||||
description: |-
|
||||
- publish_date: "2024-06-06"
|
||||
description: |-
|
||||
- R2 will now ignore the `x-purpose` request parameter.
|
||||
- publish_date: '2024-02-20'
|
||||
description: |-
|
||||
- publish_date: "2024-02-20"
|
||||
description: |-
|
||||
- When an `OPTIONS` request against the public entrypoint does not include an `origin` header, an `HTTP 400` instead of an `HTTP 401` is returned.
|
||||
- publish_date: '2024-02-06'
|
||||
description: |-
|
||||
- publish_date: "2024-02-06"
|
||||
description: |-
|
||||
- The response shape of `GET /buckets/:bucket/sippy` has changed.
|
||||
- The `/buckets/:bucket/sippy/validate` endpoint is exposed over APIGW to validate Sippy's configuration.
|
||||
- The shape of the configuration object when modifying Sippy's configuration has changed.
|
||||
- publish_date: '2024-01-30'
|
||||
description: |-
|
||||
- publish_date: "2024-01-30"
|
||||
description: |-
|
||||
- Fixed a bug where the API would accept empty strings in the `AllowedHeaders` property of `PutBucketCors` actions.
|
||||
- publish_date: '2024-01-26'
|
||||
description: |-
|
||||
- publish_date: "2024-01-26"
|
||||
description: |-
|
||||
- Parts are now automatically sorted in ascending order regardless of input during `CompleteMultipartUpload`.
|
||||
- publish_date: '2024-01-11'
|
||||
description: |-
|
||||
- publish_date: "2024-01-11"
|
||||
description: |-
|
||||
- Sippy is available for Google Cloud Storage (GCS) beta.
|
||||
- publish_date: '2023-12-11'
|
||||
description: |-
|
||||
- publish_date: "2023-12-11"
|
||||
description: |-
|
||||
- The `x-id` query param for `S3 ListBuckets` action is now ignored.
|
||||
- The `x-id` query param is now ignored for all S3 actions.
|
||||
- publish_date: '2023-10-23'
|
||||
description: |-
|
||||
- The `x-id` query param is now ignored for all S3 actions.
|
||||
- publish_date: "2023-10-23"
|
||||
description: |-
|
||||
- `PutBucketCors` now only accepts valid origins.
|
||||
- publish_date: '2023-09-01'
|
||||
description: |-
|
||||
- publish_date: "2023-09-01"
|
||||
description: |-
|
||||
- Fixed an issue with `ListBuckets` where the `name_contains` parameter would also search over the jurisdiction name.
|
||||
- publish_date: '2023-08-23'
|
||||
description: |-
|
||||
- publish_date: "2023-08-23"
|
||||
description: |-
|
||||
- Config Audit Logs GA.
|
||||
- publish_date: '2023-08-11'
|
||||
description: |-
|
||||
- publish_date: "2023-08-11"
|
||||
description: |-
|
||||
- Users can now complete conditional multipart publish operations. When a condition failure occurs when publishing an upload, the upload is no longer available and is treated as aborted.
|
||||
- publish_date: '2023-07-05'
|
||||
description: |-
|
||||
- publish_date: "2023-07-05"
|
||||
description: |-
|
||||
- Improved performance for ranged reads on very large files. Previously ranged reads near the end of very large files would be noticeably slower than
|
||||
ranged reads on smaller files. Performance should now be consistently good independent of filesize.
|
||||
- publish_date: '2023-06-21'
|
||||
description: |-
|
||||
- publish_date: "2023-06-21"
|
||||
description: |-
|
||||
- [Multipart ETags](/r2/objects/multipart-objects/#etags) are now MD5
|
||||
hashes.
|
||||
- publish_date: '2023-06-16'
|
||||
description: |-
|
||||
- Fixed a bug where calling [GetBucket](/api/operations/r2-get-bucket) on a non-existent bucket would return a 500 instead of a 404.
|
||||
- Improved S3 compatibility for ListObjectsV1, now nextmarker is only set when truncated is true.
|
||||
- The R2 worker bindings now support parsing conditional headers with multiple etags. These etags can now be strong, weak or a wildcard. Previously the bindings only accepted headers containing a single strong etag.
|
||||
- S3 putObject now supports sha256 and sha1 checksums. These were already supported by the R2 worker bindings.
|
||||
- CopyObject in the S3 compatible api now supports Cloudflare specific headers which allow the copy operation to be conditional on the state of the destination object.
|
||||
- publish_date: '2023-04-01'
|
||||
description: |-
|
||||
- [GetBucket](/api/operations/r2-get-bucket) is now available for use through the Cloudflare API.
|
||||
- [Location hints](https://developers.cloudflare.com/r2/reference/data-location/) can now be set when creating a bucket, both through the S3 API, and the dashboard.
|
||||
- publish_date: '2023-03-16'
|
||||
description: |-
|
||||
- The ListParts API has been implemented and is available for use.
|
||||
- HTTP2 is now enabled by default for new custom domains linked to R2 buckets.
|
||||
- Object Lifecycles are now available for use.
|
||||
- Bug fix: Requests to public buckets will now return the `Content-Encoding` header for gzip files when `Accept-Encoding: gzip` is used.
|
||||
- publish_date: '2023-01-27'
|
||||
description: |-
|
||||
- R2 authentication tokens created via the R2 token page are now scoped
|
||||
to a single account by default.
|
||||
- publish_date: '2022-12-07'
|
||||
description: |-
|
||||
- Fix CORS preflight requests for the S3 API, which allows using the S3 SDK in the browser.
|
||||
- Passing a range header to the `get` operation in the R2 bindings API should now work as expected.
|
||||
- publish_date: '2022-11-30'
|
||||
description: |-
|
||||
- Requests with the header `x-amz-acl: public-read` are no longer rejected.
|
||||
- Fixed issues with wildcard CORS rules and presigned URLs.
|
||||
- Fixed an issue where `ListObjects` would time out during delimited listing of unicode-normalized keys.
|
||||
- S3 API's `PutBucketCors` now rejects requests with unknown keys in the XML body.
|
||||
- Signing additional headers no longer breaks CORS preflight requests for presigned URLs.
|
||||
- publish_date: '2022-11-21'
|
||||
description: |-
|
||||
- Fixed a bug in `ListObjects` where `startAfter` would skip over objects with keys that have numbers right after the `startAfter` prefix.
|
||||
- Add worker bindings for multipart uploads.
|
||||
- publish_date: '2022-11-17'
|
||||
description: |-
|
||||
- Unconditionally return HTTP 206 on ranged requests to match behavior of other S3 compatible implementations.
|
||||
- Fixed a CORS bug where `AllowedHeaders` in the CORS config were being treated case-sensitively.
|
||||
- publish_date: '2022-11-08'
|
||||
description: |-
|
||||
- Copying multipart objects via `CopyObject` is re-enabled.
|
||||
- `UploadPartCopy` is re-enabled.
|
||||
- publish_date: '2022-10-28'
|
||||
description: |-
|
||||
- Multipart upload part sizes are always expected to be of the same size, but this enforcement is now done when you complete an upload instead of being done very time you upload a part.
|
||||
- Fixed a performance issue where concurrent multipart part uploads would get rejected.
|
||||
- publish_date: '2022-10-26'
|
||||
description: |-
|
||||
- Fixed ranged reads for multipart objects with part sizes unaligned
|
||||
to 64KiB.
|
||||
- publish_date: '2022-10-19'
|
||||
description: |-
|
||||
- `HeadBucket` now sets `x-amz-bucket-region` to `auto` in the response.
|
||||
- publish_date: '2022-10-06'
|
||||
description: |-
|
||||
- Temporarily disabled `UploadPartCopy` while we investigate an issue.
|
||||
- publish_date: '2022-09-29'
|
||||
description: |-
|
||||
- Fixed a CORS issue where `Access-Control-Allow-Headers` was not being
|
||||
set for preflight requests.
|
||||
- publish_date: '2022-09-28'
|
||||
description: |-
|
||||
- Fixed a bug where CORS configuration was not being applied to S3 endpoint.
|
||||
- No-longer render the `Access-Control-Expose-Headers` response header if `ExposeHeader` is not defined.
|
||||
- Public buckets will no-longer return the `Content-Range` response header unless the response is partial.
|
||||
- Fixed CORS rendering for the S3 `HeadObject` operation.
|
||||
- Fixed a bug where no matching CORS configuration could result in a `403` response.
|
||||
- Temporarily disable copying objects that were created with multipart uploads.
|
||||
- Fixed a bug in the Workers bindings where an internal error was being returned for malformed ranged `.get` requests.
|
||||
- publish_date: '2022-09-27'
|
||||
description: |-
|
||||
- CORS preflight responses and adding CORS headers for other responses is now implemented for S3 and public buckets. Currently, the only way to configure CORS is via the S3 API.
|
||||
- Fixup for bindings list truncation to work more correctly when listing keys with custom metadata that have `"` or when some keys/values contain certain multi-byte UTF-8 values.
|
||||
- The S3 `GetObject` operation now only returns `Content-Range` in response to a ranged request.
|
||||
- publish_date: '2022-09-19'
|
||||
description: |-
|
||||
- The R2 `put()` binding options can now be given an `onlyIf` field, similar to `get()`, that performs a conditional upload.
|
||||
- The R2 `delete()` binding now supports deleting multiple keys at once.
|
||||
- The R2 `put()` binding now supports user-specified SHA-1, SHA-256, SHA-384, SHA-512 checksums in options.
|
||||
- User-specified object checksums will now be available in the R2 `get()` and `head()` bindings response. MD5 is included by default for non-multipart uploaded objects.
|
||||
- publish_date: '2022-09-06'
|
||||
description: |-
|
||||
- The S3 `CopyObject` operation now includes `x-amz-version-id` and `x-amz-copy-source-version-id` in the response headers for consistency with other methods.
|
||||
- The `ETag` for multipart files uploaded until shortly after Open Beta uploaded now include the number of parts as a suffix.
|
||||
- publish_date: '2022-08-17'
|
||||
description: |-
|
||||
- The S3 `DeleteObjects` operation no longer trims the space from around the keys before deleting. This would result in files with leading / trailing spaces not being able to be deleted. Additionally, if there was an object with the trimmed key that existed it would be deleted instead. The S3 `DeleteObject` operation was not affected by this.
|
||||
- Fixed presigned URL support for the S3 `ListBuckets` and `ListObjects` operations.
|
||||
- publish_date: '2022-08-06'
|
||||
description: |-
|
||||
- Uploads will automatically infer the `Content-Type` based on file body
|
||||
if one is not explicitly set in the `PutObject` request. This functionality will
|
||||
come to multipart operations in the future.
|
||||
- publish_date: '2022-07-30'
|
||||
description: |-
|
||||
- Fixed S3 conditionals to work properly when provided the `LastModified` date of the last upload, bindings fixes will come in the next release.
|
||||
- `If-Match` / `If-None-Match` headers now support arrays of ETags, Weak ETags and wildcard (`*`) as per the HTTP standard and undocumented AWS S3 behavior.
|
||||
- publish_date: '2022-07-21'
|
||||
description: |-
|
||||
- Added dummy implementation of the following operation that mimics
|
||||
the response that a basic AWS S3 bucket will return when first created: `GetBucketAcl`.
|
||||
- publish_date: '2022-07-20'
|
||||
description: |-
|
||||
- Added dummy implementations of the following operations that mimic the response that a basic AWS S3 bucket will return when first created:
|
||||
- publish_date: "2023-06-16"
|
||||
description: |-
|
||||
- Fixed a bug where calling [GetBucket](/api/operations/r2-get-bucket) on a non-existent bucket would return a 500 instead of a 404.
|
||||
- Improved S3 compatibility for ListObjectsV1, now nextmarker is only set when truncated is true.
|
||||
- The R2 worker bindings now support parsing conditional headers with multiple etags. These etags can now be strong, weak or a wildcard. Previously the bindings only accepted headers containing a single strong etag.
|
||||
- S3 putObject now supports sha256 and sha1 checksums. These were already supported by the R2 worker bindings.
|
||||
- CopyObject in the S3 compatible api now supports Cloudflare specific headers which allow the copy operation to be conditional on the state of the destination object.
|
||||
- publish_date: "2023-04-01"
|
||||
description: |-
|
||||
- [GetBucket](/api/operations/r2-get-bucket) is now available for use through the Cloudflare API.
|
||||
- [Location hints](https://developers.cloudflare.com/r2/reference/data-location/) can now be set when creating a bucket, both through the S3 API, and the dashboard.
|
||||
- publish_date: "2023-03-16"
|
||||
description: |-
|
||||
- The ListParts API has been implemented and is available for use.
|
||||
- HTTP2 is now enabled by default for new custom domains linked to R2 buckets.
|
||||
- Object Lifecycles are now available for use.
|
||||
- Bug fix: Requests to public buckets will now return the `Content-Encoding` header for gzip files when `Accept-Encoding: gzip` is used.
|
||||
- publish_date: "2023-01-27"
|
||||
description: |-
|
||||
- R2 authentication tokens created via the R2 token page are now scoped
|
||||
to a single account by default.
|
||||
- publish_date: "2022-12-07"
|
||||
description: |-
|
||||
- Fix CORS preflight requests for the S3 API, which allows using the S3 SDK in the browser.
|
||||
- Passing a range header to the `get` operation in the R2 bindings API should now work as expected.
|
||||
- publish_date: "2022-11-30"
|
||||
description: |-
|
||||
- Requests with the header `x-amz-acl: public-read` are no longer rejected.
|
||||
- Fixed issues with wildcard CORS rules and presigned URLs.
|
||||
- Fixed an issue where `ListObjects` would time out during delimited listing of unicode-normalized keys.
|
||||
- S3 API's `PutBucketCors` now rejects requests with unknown keys in the XML body.
|
||||
- Signing additional headers no longer breaks CORS preflight requests for presigned URLs.
|
||||
- publish_date: "2022-11-21"
|
||||
description: |-
|
||||
- Fixed a bug in `ListObjects` where `startAfter` would skip over objects with keys that have numbers right after the `startAfter` prefix.
|
||||
- Add worker bindings for multipart uploads.
|
||||
- publish_date: "2022-11-17"
|
||||
description: |-
|
||||
- Unconditionally return HTTP 206 on ranged requests to match behavior of other S3 compatible implementations.
|
||||
- Fixed a CORS bug where `AllowedHeaders` in the CORS config were being treated case-sensitively.
|
||||
- publish_date: "2022-11-08"
|
||||
description: |-
|
||||
- Copying multipart objects via `CopyObject` is re-enabled.
|
||||
- `UploadPartCopy` is re-enabled.
|
||||
- publish_date: "2022-10-28"
|
||||
description: |-
|
||||
- Multipart upload part sizes are always expected to be of the same size, but this enforcement is now done when you complete an upload instead of being done very time you upload a part.
|
||||
- Fixed a performance issue where concurrent multipart part uploads would get rejected.
|
||||
- publish_date: "2022-10-26"
|
||||
description: |-
|
||||
- Fixed ranged reads for multipart objects with part sizes unaligned
|
||||
to 64KiB.
|
||||
- publish_date: "2022-10-19"
|
||||
description: |-
|
||||
- `HeadBucket` now sets `x-amz-bucket-region` to `auto` in the response.
|
||||
- publish_date: "2022-10-06"
|
||||
description: |-
|
||||
- Temporarily disabled `UploadPartCopy` while we investigate an issue.
|
||||
- publish_date: "2022-09-29"
|
||||
description: |-
|
||||
- Fixed a CORS issue where `Access-Control-Allow-Headers` was not being
|
||||
set for preflight requests.
|
||||
- publish_date: "2022-09-28"
|
||||
description: |-
|
||||
- Fixed a bug where CORS configuration was not being applied to S3 endpoint.
|
||||
- No-longer render the `Access-Control-Expose-Headers` response header if `ExposeHeader` is not defined.
|
||||
- Public buckets will no-longer return the `Content-Range` response header unless the response is partial.
|
||||
- Fixed CORS rendering for the S3 `HeadObject` operation.
|
||||
- Fixed a bug where no matching CORS configuration could result in a `403` response.
|
||||
- Temporarily disable copying objects that were created with multipart uploads.
|
||||
- Fixed a bug in the Workers bindings where an internal error was being returned for malformed ranged `.get` requests.
|
||||
- publish_date: "2022-09-27"
|
||||
description: |-
|
||||
- CORS preflight responses and adding CORS headers for other responses is now implemented for S3 and public buckets. Currently, the only way to configure CORS is via the S3 API.
|
||||
- Fixup for bindings list truncation to work more correctly when listing keys with custom metadata that have `"` or when some keys/values contain certain multi-byte UTF-8 values.
|
||||
- The S3 `GetObject` operation now only returns `Content-Range` in response to a ranged request.
|
||||
- publish_date: "2022-09-19"
|
||||
description: |-
|
||||
- The R2 `put()` binding options can now be given an `onlyIf` field, similar to `get()`, that performs a conditional upload.
|
||||
- The R2 `delete()` binding now supports deleting multiple keys at once.
|
||||
- The R2 `put()` binding now supports user-specified SHA-1, SHA-256, SHA-384, SHA-512 checksums in options.
|
||||
- User-specified object checksums will now be available in the R2 `get()` and `head()` bindings response. MD5 is included by default for non-multipart uploaded objects.
|
||||
- publish_date: "2022-09-06"
|
||||
description: |-
|
||||
- The S3 `CopyObject` operation now includes `x-amz-version-id` and `x-amz-copy-source-version-id` in the response headers for consistency with other methods.
|
||||
- The `ETag` for multipart files uploaded until shortly after Open Beta uploaded now include the number of parts as a suffix.
|
||||
- publish_date: "2022-08-17"
|
||||
description: |-
|
||||
- The S3 `DeleteObjects` operation no longer trims the space from around the keys before deleting. This would result in files with leading / trailing spaces not being able to be deleted. Additionally, if there was an object with the trimmed key that existed it would be deleted instead. The S3 `DeleteObject` operation was not affected by this.
|
||||
- Fixed presigned URL support for the S3 `ListBuckets` and `ListObjects` operations.
|
||||
- publish_date: "2022-08-06"
|
||||
description: |-
|
||||
- Uploads will automatically infer the `Content-Type` based on file body
|
||||
if one is not explicitly set in the `PutObject` request. This functionality will
|
||||
come to multipart operations in the future.
|
||||
- publish_date: "2022-07-30"
|
||||
description: |-
|
||||
- Fixed S3 conditionals to work properly when provided the `LastModified` date of the last upload, bindings fixes will come in the next release.
|
||||
- `If-Match` / `If-None-Match` headers now support arrays of ETags, Weak ETags and wildcard (`*`) as per the HTTP standard and undocumented AWS S3 behavior.
|
||||
- publish_date: "2022-07-21"
|
||||
description: |-
|
||||
- Added dummy implementation of the following operation that mimics
|
||||
the response that a basic AWS S3 bucket will return when first created: `GetBucketAcl`.
|
||||
- publish_date: "2022-07-20"
|
||||
description: |-
|
||||
- Added dummy implementations of the following operations that mimic the response that a basic AWS S3 bucket will return when first created:
|
||||
|
||||
- `GetBucketVersioning`
|
||||
- `GetBucketLifecycleConfiguration`
|
||||
- `GetBucketReplication`
|
||||
- `GetBucketTagging`
|
||||
- `GetObjectLockConfiguration`
|
||||
- publish_date: '2022-07-19'
|
||||
description: |-
|
||||
- Fixed an S3 compatibility issue for error responses with MinIO .NET SDK and any other tooling that expects no `xmlns` namespace attribute on the top-level `Error` tag.
|
||||
- List continuation tokens prior to 2022-07-01 are no longer accepted and must be obtained again through a new `list` operation.
|
||||
- The `list()` binding will now correctly return a smaller limit if too much data would otherwise be returned (previously would return an `Internal Error`).
|
||||
- publish_date: '2022-07-14'
|
||||
description: |-
|
||||
- Improvements to 500s: we now convert errors, so things that were previously concurrency problems for some operations should now be `TooMuchConcurrency` instead of `InternalError`. We've also reduced the rate of 500s through internal improvements.
|
||||
- `ListMultipartUpload` correctly encodes the returned `Key` if the `encoding-type` is specified.
|
||||
- publish_date: '2022-07-13'
|
||||
description: |-
|
||||
- S3 XML documents sent to R2 that have an XML declaration are not rejected with `400 Bad Request` / `MalformedXML`.
|
||||
- Minor S3 XML compatibility fix impacting Arq Backup on Windows only (not the Mac version). Response now contains XML declaration tag prefix and the xmlns attribute is present on all top-level tags in the response.
|
||||
- Beta `ListMultipartUploads` support.
|
||||
- publish_date: '2022-07-06'
|
||||
description: |-
|
||||
- Support the `r2_list_honor_include` compat flag coming up in an upcoming runtime release (default behavior as of 2022-07-14 compat date). Without that compat flag/date, list will continue to function implicitly as `include: ['httpMetadata', 'customMetadata']` regardless of what you specify.
|
||||
- `cf-create-bucket-if-missing` can be set on a `PutObject`/`CreateMultipartUpload` request to implicitly create the bucket if it does not exist.
|
||||
- Fix S3 compatibility with MinIO client spec non-compliant XML for publishing multipart uploads. Any leading and trailing quotes in `CompleteMultipartUpload` are now optional and ignored as it seems to be the actual non-standard behavior AWS implements.
|
||||
- publish_date: '2022-07-01'
|
||||
description: |-
|
||||
- Unsupported search parameters to `ListObjects`/`ListObjectsV2` are
|
||||
now rejected with `501 Not Implemented`.
|
||||
- Fixes for Listing:
|
||||
- Fix listing behavior when the number of files within a folder exceeds the limit (you'd end
|
||||
up seeing a CommonPrefix for that large folder N times where N = number of children
|
||||
within the CommonPrefix / limit).
|
||||
- Fix corner case where listing could cause
|
||||
objects with sharing the base name of a \"folder\" to be skipped.
|
||||
- Fix listing over some files that shared a certain common prefix.
|
||||
- `DeleteObjects` can now handle 1000 objects at a time.
|
||||
- S3 `CreateBucket` request can specify `x-amz-bucket-object-lock-enabled` with a value of `false` and not have the requested rejected with a `NotImplemented`
|
||||
error. A value of `true` will continue to be rejected as R2 does not yet support
|
||||
object locks.
|
||||
- publish_date: '2022-06-17'
|
||||
description: |-
|
||||
- Fixed a regression for some clients when using an empty delimiter.
|
||||
- Added support for S3 pre-signed URLs.
|
||||
- publish_date: '2022-06-16'
|
||||
description: |-
|
||||
- Fixed a regression in the S3 API `UploadPart` operation where `TooMuchConcurrency`
|
||||
& `NoSuchUpload` errors were being returned as `NoSuchBucket`.
|
||||
- publish_date: '2022-06-13'
|
||||
description: |-
|
||||
- Fixed a bug with the S3 API `ListObjectsV2` operation not returning empty folder/s as common prefixes when using delimiters.
|
||||
- The S3 API `ListObjectsV2` `KeyCount` parameter now correctly returns the sum of keys and common prefixes rather than just the keys.
|
||||
- Invalid cursors for list operations no longer fail with an `InternalError` and now return the appropriate error message.
|
||||
- publish_date: '2022-06-10'
|
||||
description: |-
|
||||
- The `ContinuationToken` field is now correctly returned in the response if provided in a S3 API `ListObjectsV2` request.
|
||||
- Fixed a bug where the S3 API `AbortMultipartUpload` operation threw an error when called multiple times.
|
||||
- publish_date: '2022-05-27'
|
||||
description: |-
|
||||
- Fixed a bug where the S3 API's `PutObject` or the `.put()` binding could fail but still show the bucket upload as successful.
|
||||
- If [conditional headers](https://datatracker.ietf.org/doc/html/rfc7232) are provided to S3 API `UploadObject` or `CreateMultipartUpload` operations, and the object exists, a `412 Precondition Failed` status code will be returned if these checks are not met.
|
||||
- publish_date: '2022-05-20'
|
||||
description: |-
|
||||
- Fixed a bug when `Accept-Encoding` was being used in `SignedHeaders`
|
||||
when sending requests to the S3 API would result in a `SignatureDoesNotMatch`
|
||||
response.
|
||||
- publish_date: '2022-05-17'
|
||||
description: |-
|
||||
- Fixed a bug where requests to the S3 API were not handling non-encoded parameters used for the authorization signature.
|
||||
- Fixed a bug where requests to the S3 API where number-like keys were being parsed as numbers instead of strings.
|
||||
- publish_date: '2022-05-16'
|
||||
description: |-
|
||||
- Add support for S3 [virtual-hosted style paths](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html), such as `<BUCKET>.<ACCOUNT_ID>.r2.cloudflarestorage.com` instead of path-based routing (`<ACCOUNT_ID>.r2.cloudflarestorage.com/<BUCKET>`).
|
||||
- Implemented `GetBucketLocation` for compatibility with external tools, this will always return a `LocationConstraint` of `auto`.
|
||||
- publish_date: '2022-05-06'
|
||||
description: |-
|
||||
- S3 API `GetObject` ranges are now inclusive (`bytes=0-0` will correctly return the first byte).
|
||||
- S3 API `GetObject` partial reads return the proper `206 Partial Content` response code.
|
||||
- Copying from a non-existent key (or from a non-existent bucket) to another bucket now returns the proper `NoSuchKey` / `NoSuchBucket` response.
|
||||
- The S3 API now returns the proper `Content-Type: application/xml` response header on relevant endpoints.
|
||||
- Multipart uploads now have a `-N` suffix on the etag representing the number of parts the file was published with.
|
||||
- `UploadPart` and `UploadPartCopy` now return proper error messages, such as `TooMuchConcurrency` or `NoSuchUpload`, instead of 'internal error'.
|
||||
- `UploadPart` can now be sent a 0-length part.
|
||||
- publish_date: '2022-05-05'
|
||||
description: |-
|
||||
- When using the S3 API, an empty string and `us-east-1` will now alias to the `auto` region for compatibility with external tools.
|
||||
- `GetBucketEncryption`, `PutBucketEncryption` and `DeleteBucketEncrypotion` are now supported (the only supported value currently is `AES256`).
|
||||
- Unsupported operations are explicitly rejected as unimplemented rather than implicitly converting them into `ListObjectsV2`/`PutBucket`/`DeleteBucket` respectively.
|
||||
- S3 API `CompleteMultipartUploads` requests are now properly escaped.
|
||||
- publish_date: '2022-05-03'
|
||||
description: |-
|
||||
- Pagination cursors are no longer returned when the keys in a bucket is the same as the `MaxKeys` argument.
|
||||
- The S3 API `ListBuckets` operation now accepts `cf-max-keys`, `cf-start-after` and `cf-continuation-token` headers behave the same as the respective URL parameters.
|
||||
- The S3 API `ListBuckets` and `ListObjects` endpoints now allow `per_page` to be 0.
|
||||
- The S3 API `CopyObject` source parameter now requires a leading slash.
|
||||
- The S3 API `CopyObject` operation now returns a `NoSuchBucket` error when copying to a non-existent bucket instead of an internal error.
|
||||
- Enforce the requirement for `auto` in SigV4 signing and the `CreateBucket` `LocationConstraint` parameter.
|
||||
- The S3 API `CreateBucket` operation now returns the proper `location` response header.
|
||||
- publish_date: '2022-04-14'
|
||||
description: |-
|
||||
- The S3 API now supports unchunked signed payloads.
|
||||
- Fixed `.put()` for the Workers R2 bindings.
|
||||
- Fixed a regression where key names were not properly decoded when using the S3 API.
|
||||
- Fixed a bug where deleting an object and then another object which is a prefix of the first could result in errors.
|
||||
- The S3 API `DeleteObjects` operation no longer returns an error even though an object has been deleted in some cases.
|
||||
- Fixed a bug where `startAfter` and `continuationToken` were not working in list operations.
|
||||
- The S3 API `ListObjects` operation now correctly renders `Prefix`, `Delimiter`, `StartAfter` and `MaxKeys` in the response.
|
||||
- The S3 API `ListObjectsV2` now correctly honors the `encoding-type` parameter.
|
||||
- The S3 API `PutObject` operation now works with `POST` requests for `s3cmd` compatibility.
|
||||
- publish_date: '2022-04-04'
|
||||
description: |-
|
||||
- The S3 API `DeleteObjects` request now properly returns a `MalformedXML`
|
||||
error instead of `InternalError` when provided with more than 128 keys.
|
||||
- `GetBucketVersioning`
|
||||
- `GetBucketLifecycleConfiguration`
|
||||
- `GetBucketReplication`
|
||||
- `GetBucketTagging`
|
||||
- `GetObjectLockConfiguration`
|
||||
- publish_date: "2022-07-19"
|
||||
description: |-
|
||||
- Fixed an S3 compatibility issue for error responses with MinIO .NET SDK and any other tooling that expects no `xmlns` namespace attribute on the top-level `Error` tag.
|
||||
- List continuation tokens prior to 2022-07-01 are no longer accepted and must be obtained again through a new `list` operation.
|
||||
- The `list()` binding will now correctly return a smaller limit if too much data would otherwise be returned (previously would return an `Internal Error`).
|
||||
- publish_date: "2022-07-14"
|
||||
description: |-
|
||||
- Improvements to 500s: we now convert errors, so things that were previously concurrency problems for some operations should now be `TooMuchConcurrency` instead of `InternalError`. We've also reduced the rate of 500s through internal improvements.
|
||||
- `ListMultipartUpload` correctly encodes the returned `Key` if the `encoding-type` is specified.
|
||||
- publish_date: "2022-07-13"
|
||||
description: |-
|
||||
- S3 XML documents sent to R2 that have an XML declaration are not rejected with `400 Bad Request` / `MalformedXML`.
|
||||
- Minor S3 XML compatibility fix impacting Arq Backup on Windows only (not the Mac version). Response now contains XML declaration tag prefix and the xmlns attribute is present on all top-level tags in the response.
|
||||
- Beta `ListMultipartUploads` support.
|
||||
- publish_date: "2022-07-06"
|
||||
description: |-
|
||||
- Support the `r2_list_honor_include` compat flag coming up in an upcoming runtime release (default behavior as of 2022-07-14 compat date). Without that compat flag/date, list will continue to function implicitly as `include: ['httpMetadata', 'customMetadata']` regardless of what you specify.
|
||||
- `cf-create-bucket-if-missing` can be set on a `PutObject`/`CreateMultipartUpload` request to implicitly create the bucket if it does not exist.
|
||||
- Fix S3 compatibility with MinIO client spec non-compliant XML for publishing multipart uploads. Any leading and trailing quotes in `CompleteMultipartUpload` are now optional and ignored as it seems to be the actual non-standard behavior AWS implements.
|
||||
- publish_date: "2022-07-01"
|
||||
description: |-
|
||||
- Unsupported search parameters to `ListObjects`/`ListObjectsV2` are
|
||||
now rejected with `501 Not Implemented`.
|
||||
- Fixes for Listing:
|
||||
- Fix listing behavior when the number of files within a folder exceeds the limit (you'd end
|
||||
up seeing a CommonPrefix for that large folder N times where N = number of children
|
||||
within the CommonPrefix / limit).
|
||||
- Fix corner case where listing could cause
|
||||
objects with sharing the base name of a \"folder\" to be skipped.
|
||||
- Fix listing over some files that shared a certain common prefix.
|
||||
- `DeleteObjects` can now handle 1000 objects at a time.
|
||||
- S3 `CreateBucket` request can specify `x-amz-bucket-object-lock-enabled` with a value of `false` and not have the requested rejected with a `NotImplemented`
|
||||
error. A value of `true` will continue to be rejected as R2 does not yet support
|
||||
object locks.
|
||||
- publish_date: "2022-06-17"
|
||||
description: |-
|
||||
- Fixed a regression for some clients when using an empty delimiter.
|
||||
- Added support for S3 pre-signed URLs.
|
||||
- publish_date: "2022-06-16"
|
||||
description: |-
|
||||
- Fixed a regression in the S3 API `UploadPart` operation where `TooMuchConcurrency`
|
||||
& `NoSuchUpload` errors were being returned as `NoSuchBucket`.
|
||||
- publish_date: "2022-06-13"
|
||||
description: |-
|
||||
- Fixed a bug with the S3 API `ListObjectsV2` operation not returning empty folder/s as common prefixes when using delimiters.
|
||||
- The S3 API `ListObjectsV2` `KeyCount` parameter now correctly returns the sum of keys and common prefixes rather than just the keys.
|
||||
- Invalid cursors for list operations no longer fail with an `InternalError` and now return the appropriate error message.
|
||||
- publish_date: "2022-06-10"
|
||||
description: |-
|
||||
- The `ContinuationToken` field is now correctly returned in the response if provided in a S3 API `ListObjectsV2` request.
|
||||
- Fixed a bug where the S3 API `AbortMultipartUpload` operation threw an error when called multiple times.
|
||||
- publish_date: "2022-05-27"
|
||||
description: |-
|
||||
- Fixed a bug where the S3 API's `PutObject` or the `.put()` binding could fail but still show the bucket upload as successful.
|
||||
- If [conditional headers](https://datatracker.ietf.org/doc/html/rfc7232) are provided to S3 API `UploadObject` or `CreateMultipartUpload` operations, and the object exists, a `412 Precondition Failed` status code will be returned if these checks are not met.
|
||||
- publish_date: "2022-05-20"
|
||||
description: |-
|
||||
- Fixed a bug when `Accept-Encoding` was being used in `SignedHeaders`
|
||||
when sending requests to the S3 API would result in a `SignatureDoesNotMatch`
|
||||
response.
|
||||
- publish_date: "2022-05-17"
|
||||
description: |-
|
||||
- Fixed a bug where requests to the S3 API were not handling non-encoded parameters used for the authorization signature.
|
||||
- Fixed a bug where requests to the S3 API where number-like keys were being parsed as numbers instead of strings.
|
||||
- publish_date: "2022-05-16"
|
||||
description: |-
|
||||
- Add support for S3 [virtual-hosted style paths](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html), such as `<BUCKET>.<ACCOUNT_ID>.r2.cloudflarestorage.com` instead of path-based routing (`<ACCOUNT_ID>.r2.cloudflarestorage.com/<BUCKET>`).
|
||||
- Implemented `GetBucketLocation` for compatibility with external tools, this will always return a `LocationConstraint` of `auto`.
|
||||
- publish_date: "2022-05-06"
|
||||
description: |-
|
||||
- S3 API `GetObject` ranges are now inclusive (`bytes=0-0` will correctly return the first byte).
|
||||
- S3 API `GetObject` partial reads return the proper `206 Partial Content` response code.
|
||||
- Copying from a non-existent key (or from a non-existent bucket) to another bucket now returns the proper `NoSuchKey` / `NoSuchBucket` response.
|
||||
- The S3 API now returns the proper `Content-Type: application/xml` response header on relevant endpoints.
|
||||
- Multipart uploads now have a `-N` suffix on the etag representing the number of parts the file was published with.
|
||||
- `UploadPart` and `UploadPartCopy` now return proper error messages, such as `TooMuchConcurrency` or `NoSuchUpload`, instead of 'internal error'.
|
||||
- `UploadPart` can now be sent a 0-length part.
|
||||
- publish_date: "2022-05-05"
|
||||
description: |-
|
||||
- When using the S3 API, an empty string and `us-east-1` will now alias to the `auto` region for compatibility with external tools.
|
||||
- `GetBucketEncryption`, `PutBucketEncryption` and `DeleteBucketEncrypotion` are now supported (the only supported value currently is `AES256`).
|
||||
- Unsupported operations are explicitly rejected as unimplemented rather than implicitly converting them into `ListObjectsV2`/`PutBucket`/`DeleteBucket` respectively.
|
||||
- S3 API `CompleteMultipartUploads` requests are now properly escaped.
|
||||
- publish_date: "2022-05-03"
|
||||
description: |-
|
||||
- Pagination cursors are no longer returned when the keys in a bucket is the same as the `MaxKeys` argument.
|
||||
- The S3 API `ListBuckets` operation now accepts `cf-max-keys`, `cf-start-after` and `cf-continuation-token` headers behave the same as the respective URL parameters.
|
||||
- The S3 API `ListBuckets` and `ListObjects` endpoints now allow `per_page` to be 0.
|
||||
- The S3 API `CopyObject` source parameter now requires a leading slash.
|
||||
- The S3 API `CopyObject` operation now returns a `NoSuchBucket` error when copying to a non-existent bucket instead of an internal error.
|
||||
- Enforce the requirement for `auto` in SigV4 signing and the `CreateBucket` `LocationConstraint` parameter.
|
||||
- The S3 API `CreateBucket` operation now returns the proper `location` response header.
|
||||
- publish_date: "2022-04-14"
|
||||
description: |-
|
||||
- The S3 API now supports unchunked signed payloads.
|
||||
- Fixed `.put()` for the Workers R2 bindings.
|
||||
- Fixed a regression where key names were not properly decoded when using the S3 API.
|
||||
- Fixed a bug where deleting an object and then another object which is a prefix of the first could result in errors.
|
||||
- The S3 API `DeleteObjects` operation no longer returns an error even though an object has been deleted in some cases.
|
||||
- Fixed a bug where `startAfter` and `continuationToken` were not working in list operations.
|
||||
- The S3 API `ListObjects` operation now correctly renders `Prefix`, `Delimiter`, `StartAfter` and `MaxKeys` in the response.
|
||||
- The S3 API `ListObjectsV2` now correctly honors the `encoding-type` parameter.
|
||||
- The S3 API `PutObject` operation now works with `POST` requests for `s3cmd` compatibility.
|
||||
- publish_date: "2022-04-04"
|
||||
description: |-
|
||||
- The S3 API `DeleteObjects` request now properly returns a `MalformedXML`
|
||||
error instead of `InternalError` when provided with more than 128 keys.
|
||||
|
|
|
|||
|
|
@ -5,113 +5,113 @@ productLink: "/radar/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-06-27'
|
||||
title: Change TCP connection tampering API endpoints to TCP Resets Timeouts
|
||||
description: |-
|
||||
* Changed the connection tampering summary and timeseries API endpoints to
|
||||
TCP resets timeouts [summary](/api/operations/radar-get-tcp-resets-timeouts-summary)
|
||||
and [timeseries](/api/operations/radar-get-tcp-resets-timeouts-timeseries-group),
|
||||
respectively.
|
||||
- publish_date: '2023-11-27'
|
||||
title: Add more meta information's
|
||||
description: |-
|
||||
* Added meta.lastUpdated to all summaries and top endpoints (timeseries and timeseriesGroups already had this).
|
||||
* Fix meta.dateRange to return date ranges for all requested series.
|
||||
- publish_date: '2023-11-16'
|
||||
title: Add new Layer 3 endpoints and Layer 7 dimensions
|
||||
description: |-
|
||||
* Added Layer 3 [top origin locations](/api/operations/radar-get-attacks-layer3-top-origin-locations)
|
||||
and [top target location](/api/operations/radar-get-attacks-layer3-top-target-locations).
|
||||
* Added Layer 7 Summaries by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`.
|
||||
* Added Layer 7 Timeseries Groups by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`, `industry`, `vertical`.
|
||||
* Added Layer 7 Top by `industry`, `vertical`.
|
||||
* Deprecated Layer 7 [timeseries groups without dimension](/api/operations/radar-get-attacks-layer7-timeseries-group).
|
||||
* To continue getting this data, switch to the new
|
||||
[timeseries group by mitigation_product](/api/operations/radar-get-attacks-layer7-timeseries-group-by-mitigation-product)
|
||||
endpoint.
|
||||
* Deprecated Layer 7 [summary without dimension)](/api/operations/radar-get-attacks-layer7-summary).
|
||||
* To continue getting this data, switch to the new
|
||||
[summary by mitigation_product](/api/operations/radar-get-attacks-layer7-summary-by-mitigation-product)
|
||||
endpoint.
|
||||
* Added new [Error codes](/radar/get-started/error-codes/).
|
||||
- publish_date: '2023-10-31'
|
||||
title: Add new Layer 3 direction parameter
|
||||
description: |-
|
||||
* Added a `direction` parameter to all Layer 3 endpoints. Use together with `location` parameter to filter by origin or
|
||||
target location [timeseries groups](/api/operations/radar-get-attacks-layer3-timeseries-group-by-vector).
|
||||
- publish_date: '2023-09-08'
|
||||
title: Add Connection Tampering endpoints
|
||||
description: |-
|
||||
* Added Connection Tampering [summary](/api/operations/radar-get-tcp-resets-timeouts-summary)
|
||||
and [timeseries](/api/operations/radar-get-tcp-resets-timeouts-timeseries-group) endpoints.
|
||||
- publish_date: '2023-08-14'
|
||||
title: Deprecate old layer 3 dataset
|
||||
description: |-
|
||||
* Added Regional Internet Registry (see field `source` in response)
|
||||
to [get asn by id](/api/operations/radar-get-entities-asn-by-id)
|
||||
and [get asn by ip](/api/operations/radar-get-entities-asn-by-ip) endpoints.
|
||||
* Stopped collecting data in the old Layer 3 data source.
|
||||
* Updated Layer 3
|
||||
[timeseries](/api/operations/radar-get-attacks-layer3-timeseries-by-bytes) endpoint
|
||||
to start using the new Layer 3 data source by default, fetching the old data source now requires sending the parameter
|
||||
`metric=bytes_old`.
|
||||
* Deprecated Layer 3
|
||||
[summary](/api/operations/radar-get-attacks-layer3-summary) endpoint, this will stop
|
||||
receiving data after 2023-08-14.
|
||||
* To continue getting this data, switch to the
|
||||
new [timeseries group protocol](/api/operations/radar-get-attacks-layer3-summary-by-protocol)
|
||||
endpoint.
|
||||
* Deprecated Layer 3
|
||||
[timeseries groups](/api/operations/radar-get-attacks-layer3-timeseries-groups)
|
||||
endpoint, this will stop receiving data after 2023-08-14.
|
||||
* To continue getting this data, switch to the
|
||||
new [timeseries group protocol](/api/operations/radar-get-attacks-layer3-timeseries-group-by-protocol)
|
||||
endpoint.
|
||||
- publish_date: '2023-07-31'
|
||||
title: Fix HTTP timeseries endpoint urls
|
||||
description: |-
|
||||
* Updated HTTP `timeseries` endpoints urls
|
||||
to `timeseries_groups` ([example](/api/operations/radar-get-http-timeseries-group-by-browser-families))
|
||||
due to consistency. Old timeseries endpoints are still available, but will soon be removed.
|
||||
- publish_date: '2023-07-20'
|
||||
title: Add URL Scanner endpoints
|
||||
description: |-
|
||||
* Added [urlscanner endpoints](/api/operations/urlscanner-search-scans). For more information, refer to [URL Scanner](/radar/investigate/url-scanner/).
|
||||
- publish_date: '2023-06-20'
|
||||
title: Add Quality endpoints
|
||||
description: |-
|
||||
* Added [quality endpoints](/api/operations/radar-get-quality-index-summary).
|
||||
- publish_date: '2023-06-07'
|
||||
title: Add BGP stats, pfx2as and moas endpoint
|
||||
description: |-
|
||||
* Added BGP [stats](/api/operations/radar-get-bgp-routes-stats),
|
||||
[pfx2as](/api/operations/radar-get-bgp-pfx2as)
|
||||
and [moas](/api/operations/radar-get-bgp-pfx2as-moas) endpoints.
|
||||
- publish_date: '2023-05-10'
|
||||
title: Added `IOS` as an option for the OS parameter in all HTTP
|
||||
description: |-
|
||||
* Added `IOS` as an option for the OS parameter in all HTTP
|
||||
endpoints ([example](/api/operations/radar-get-http-summary-by-bot-class)).
|
||||
- publish_date: '2023-03-20'
|
||||
title: Add AS112 and email endpoints
|
||||
description: |-
|
||||
* Added [AS112 endpoints](/api/operations/radar-get-dns-as112-timeseries-by-dnssec).
|
||||
* Added [email endpoints](/api/operations/radar-get-email-security-summary-by-arc).
|
||||
- publish_date: '2023-01-23'
|
||||
title: Updated IPv6 calculation method
|
||||
description: |-
|
||||
* IPv6 percentage started to be calculated as (IPv6 requests / requests for dual-stacked content), where as before it
|
||||
was calculated as (IPv6 requests / IPv4+IPv6 requests).
|
||||
- publish_date: '2023-01-11'
|
||||
title: Add new layer 3 dataset
|
||||
description: |-
|
||||
* Added new Layer 3 data source and related endpoints.
|
||||
* Updated Layer 3
|
||||
[timeseries](/api/operations/radar-get-attacks-layer3-timeseries-by-bytes) endpoint
|
||||
to support fetching both current and new data sources. For retro-compatibility
|
||||
reasons, fetching the new data source requires sending the parameter `metric=bytes` else the current data
|
||||
source will be returned.
|
||||
* Deprecated old Layer 3 endpoints
|
||||
[TimeseriesGroups](/api/operations/radar-get-attacks-layer3-timeseries-groups) and
|
||||
[Summary](/api/operations/radar-get-attacks-layer3-summary).
|
||||
Users should upgrade to newer endpoints.
|
||||
- publish_date: "2024-06-27"
|
||||
title: Change TCP connection tampering API endpoints to TCP Resets Timeouts
|
||||
description: |-
|
||||
* Changed the connection tampering summary and timeseries API endpoints to
|
||||
TCP resets timeouts [summary](/api/operations/radar-get-tcp-resets-timeouts-summary)
|
||||
and [timeseries](/api/operations/radar-get-tcp-resets-timeouts-timeseries-group),
|
||||
respectively.
|
||||
- publish_date: "2023-11-27"
|
||||
title: Add more meta information's
|
||||
description: |-
|
||||
* Added meta.lastUpdated to all summaries and top endpoints (timeseries and timeseriesGroups already had this).
|
||||
* Fix meta.dateRange to return date ranges for all requested series.
|
||||
- publish_date: "2023-11-16"
|
||||
title: Add new Layer 3 endpoints and Layer 7 dimensions
|
||||
description: |-
|
||||
* Added Layer 3 [top origin locations](/api/operations/radar-get-attacks-layer3-top-origin-locations)
|
||||
and [top target location](/api/operations/radar-get-attacks-layer3-top-target-locations).
|
||||
* Added Layer 7 Summaries by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`.
|
||||
* Added Layer 7 Timeseries Groups by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`, `industry`, `vertical`.
|
||||
* Added Layer 7 Top by `industry`, `vertical`.
|
||||
* Deprecated Layer 7 [timeseries groups without dimension](/api/operations/radar-get-attacks-layer7-timeseries-group).
|
||||
* To continue getting this data, switch to the new
|
||||
[timeseries group by mitigation_product](/api/operations/radar-get-attacks-layer7-timeseries-group-by-mitigation-product)
|
||||
endpoint.
|
||||
* Deprecated Layer 7 [summary without dimension)](/api/operations/radar-get-attacks-layer7-summary).
|
||||
* To continue getting this data, switch to the new
|
||||
[summary by mitigation_product](/api/operations/radar-get-attacks-layer7-summary-by-mitigation-product)
|
||||
endpoint.
|
||||
* Added new [Error codes](/radar/get-started/error-codes/).
|
||||
- publish_date: "2023-10-31"
|
||||
title: Add new Layer 3 direction parameter
|
||||
description: |-
|
||||
* Added a `direction` parameter to all Layer 3 endpoints. Use together with `location` parameter to filter by origin or
|
||||
target location [timeseries groups](/api/operations/radar-get-attacks-layer3-timeseries-group-by-vector).
|
||||
- publish_date: "2023-09-08"
|
||||
title: Add Connection Tampering endpoints
|
||||
description: |-
|
||||
* Added Connection Tampering [summary](/api/operations/radar-get-tcp-resets-timeouts-summary)
|
||||
and [timeseries](/api/operations/radar-get-tcp-resets-timeouts-timeseries-group) endpoints.
|
||||
- publish_date: "2023-08-14"
|
||||
title: Deprecate old layer 3 dataset
|
||||
description: |-
|
||||
* Added Regional Internet Registry (see field `source` in response)
|
||||
to [get asn by id](/api/operations/radar-get-entities-asn-by-id)
|
||||
and [get asn by ip](/api/operations/radar-get-entities-asn-by-ip) endpoints.
|
||||
* Stopped collecting data in the old Layer 3 data source.
|
||||
* Updated Layer 3
|
||||
[timeseries](/api/operations/radar-get-attacks-layer3-timeseries-by-bytes) endpoint
|
||||
to start using the new Layer 3 data source by default, fetching the old data source now requires sending the parameter
|
||||
`metric=bytes_old`.
|
||||
* Deprecated Layer 3
|
||||
[summary](/api/operations/radar-get-attacks-layer3-summary) endpoint, this will stop
|
||||
receiving data after 2023-08-14.
|
||||
* To continue getting this data, switch to the
|
||||
new [timeseries group protocol](/api/operations/radar-get-attacks-layer3-summary-by-protocol)
|
||||
endpoint.
|
||||
* Deprecated Layer 3
|
||||
[timeseries groups](/api/operations/radar-get-attacks-layer3-timeseries-groups)
|
||||
endpoint, this will stop receiving data after 2023-08-14.
|
||||
* To continue getting this data, switch to the
|
||||
new [timeseries group protocol](/api/operations/radar-get-attacks-layer3-timeseries-group-by-protocol)
|
||||
endpoint.
|
||||
- publish_date: "2023-07-31"
|
||||
title: Fix HTTP timeseries endpoint urls
|
||||
description: |-
|
||||
* Updated HTTP `timeseries` endpoints urls
|
||||
to `timeseries_groups` ([example](/api/operations/radar-get-http-timeseries-group-by-browser-families))
|
||||
due to consistency. Old timeseries endpoints are still available, but will soon be removed.
|
||||
- publish_date: "2023-07-20"
|
||||
title: Add URL Scanner endpoints
|
||||
description: |-
|
||||
* Added [urlscanner endpoints](/api/operations/urlscanner-search-scans). For more information, refer to [URL Scanner](/radar/investigate/url-scanner/).
|
||||
- publish_date: "2023-06-20"
|
||||
title: Add Quality endpoints
|
||||
description: |-
|
||||
* Added [quality endpoints](/api/operations/radar-get-quality-index-summary).
|
||||
- publish_date: "2023-06-07"
|
||||
title: Add BGP stats, pfx2as and moas endpoint
|
||||
description: |-
|
||||
* Added BGP [stats](/api/operations/radar-get-bgp-routes-stats),
|
||||
[pfx2as](/api/operations/radar-get-bgp-pfx2as)
|
||||
and [moas](/api/operations/radar-get-bgp-pfx2as-moas) endpoints.
|
||||
- publish_date: "2023-05-10"
|
||||
title: Added `IOS` as an option for the OS parameter in all HTTP
|
||||
description: |-
|
||||
* Added `IOS` as an option for the OS parameter in all HTTP
|
||||
endpoints ([example](/api/operations/radar-get-http-summary-by-bot-class)).
|
||||
- publish_date: "2023-03-20"
|
||||
title: Add AS112 and email endpoints
|
||||
description: |-
|
||||
* Added [AS112 endpoints](/api/operations/radar-get-dns-as112-timeseries-by-dnssec).
|
||||
* Added [email endpoints](/api/operations/radar-get-email-security-summary-by-arc).
|
||||
- publish_date: "2023-01-23"
|
||||
title: Updated IPv6 calculation method
|
||||
description: |-
|
||||
* IPv6 percentage started to be calculated as (IPv6 requests / requests for dual-stacked content), where as before it
|
||||
was calculated as (IPv6 requests / IPv4+IPv6 requests).
|
||||
- publish_date: "2023-01-11"
|
||||
title: Add new layer 3 dataset
|
||||
description: |-
|
||||
* Added new Layer 3 data source and related endpoints.
|
||||
* Updated Layer 3
|
||||
[timeseries](/api/operations/radar-get-attacks-layer3-timeseries-by-bytes) endpoint
|
||||
to support fetching both current and new data sources. For retro-compatibility
|
||||
reasons, fetching the new data source requires sending the parameter `metric=bytes` else the current data
|
||||
source will be returned.
|
||||
* Deprecated old Layer 3 endpoints
|
||||
[TimeseriesGroups](/api/operations/radar-get-attacks-layer3-timeseries-groups) and
|
||||
[Summary](/api/operations/radar-get-attacks-layer3-summary).
|
||||
Users should upgrade to newer endpoints.
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@ productLink: "/cloudflare-one/insights/risk-score/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-06-17'
|
||||
title: Okta risk exchange
|
||||
description: |-
|
||||
You can now [exchange user risk scores](/cloudflare-one/insights/risk-score/#send-risk-score-to-okta) with Okta to inform SSO-level policies.
|
||||
- publish_date: '2024-06-14'
|
||||
title: SentinelOne signal ingestion
|
||||
description: |-
|
||||
You can now configure a [predefined risk behavior](/cloudflare-one/insights/risk-score/#predefined-risk-behaviors) to evaluate user risk score using device posture attributes from the [SentinelOne integration](/cloudflare-one/identity/devices/service-providers/sentinelone/).
|
||||
- publish_date: "2024-06-17"
|
||||
title: Okta risk exchange
|
||||
description: |-
|
||||
You can now [exchange user risk scores](/cloudflare-one/insights/risk-score/#send-risk-score-to-okta) with Okta to inform SSO-level policies.
|
||||
- publish_date: "2024-06-14"
|
||||
title: SentinelOne signal ingestion
|
||||
description: |-
|
||||
You can now configure a [predefined risk behavior](/cloudflare-one/insights/risk-score/#predefined-risk-behaviors) to evaluate user risk score using device posture attributes from the [SentinelOne integration](/cloudflare-one/identity/devices/service-providers/sentinelone/).
|
||||
|
|
|
|||
|
|
@ -5,6 +5,6 @@ productLink: "/security-center/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-07-22'
|
||||
description: |-
|
||||
- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
|
||||
- publish_date: "2024-07-22"
|
||||
description: |-
|
||||
- Customers can now archive multiple Security Insights at the same time. Go to **Security Center** > **Security Insights** and select the insights to archive.
|
||||
|
|
|
|||
|
|
@ -5,328 +5,358 @@ productLink: "/stream/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-08-15'
|
||||
title: Full HD encoding for Portrait Videos
|
||||
description: |-
|
||||
Stream now supports full HD encoding for portrait/vertical videos. Videos with a height greater than their width will now be constrained and prepared for adaptive bitrate renditions based on their width. No changes are required to benefit from this update. For more information, refer to [the announcement](https://blog.cloudflare.com/introducing-high-definition-portrait-video-support-for-cloudflare-stream).
|
||||
- publish_date: '2024-08-09'
|
||||
title: Hide Viewer Count in Live Streams
|
||||
description: |-
|
||||
A new property `hideLiveViewerCount` has been added to Live Inputs to block access to the count of viewers in a live stream and remove it from the player. For more information, refer to [Start a Live Stream](/stream/stream-live/start-stream-live/).
|
||||
- publish_date: '2024-07-23'
|
||||
title: New Live Webhooks for Error States
|
||||
description: |-
|
||||
Stream has added a new notification event for Live broadcasts to alert (via email or webhook) on various error conditions including unsupported codecs, bad GOP/keyframe interval, or quota exhaustion.
|
||||
- publish_date: "2024-08-15"
|
||||
title: Full HD encoding for Portrait Videos
|
||||
description: |-
|
||||
Stream now supports full HD encoding for portrait/vertical videos. Videos with a height greater than their width will now be constrained and prepared for adaptive bitrate renditions based on their width. No changes are required to benefit from this update. For more information, refer to [the announcement](https://blog.cloudflare.com/introducing-high-definition-portrait-video-support-for-cloudflare-stream).
|
||||
- publish_date: "2024-08-09"
|
||||
title: Hide Viewer Count in Live Streams
|
||||
description: |-
|
||||
A new property `hideLiveViewerCount` has been added to Live Inputs to block access to the count of viewers in a live stream and remove it from the player. For more information, refer to [Start a Live Stream](/stream/stream-live/start-stream-live/).
|
||||
- publish_date: "2024-07-23"
|
||||
title: New Live Webhooks for Error States
|
||||
description: |-
|
||||
Stream has added a new notification event for Live broadcasts to alert (via email or webhook) on various error conditions including unsupported codecs, bad GOP/keyframe interval, or quota exhaustion.
|
||||
|
||||
When creating/editing a notification, subscribe to `live_input.errored` to receive the new event type. Existing notification subscriptions will not be changed automatically. For more information, refer to [Receive Live Webhooks](/stream/stream-live/webhooks/).
|
||||
- publish_date: '2024-06-20'
|
||||
title: Generated Captions to Open beta
|
||||
description: |-
|
||||
Stream has introduced automatically generated captions to open beta for all subscribers at no additional cost. While in beta, only English is supported and videos must be less than 2 hours. For more information, refer to the [product announcement and deep dive](https://blog.cloudflare.com/stream-automatic-captions-with-ai) or refer to the [captions documentation](/stream/edit-videos/adding-captions/) to get started.
|
||||
- publish_date: '2024-06-11'
|
||||
title: Updated response codes on requests for errored videos
|
||||
description: |-
|
||||
Stream will now return HTTP error status 424 (failed dependency) when requesting segments, manifests, thumbnails, downloads, or subtitles for videos that are in an errored state. Previously, Stream would return one of several 5xx codes for requests like this.
|
||||
- publish_date: '2024-04-11'
|
||||
title: Live Instant Clipping for live broadcasts and recordings
|
||||
description: |-
|
||||
Clipping is now available in open beta for live broadcasts and recordings. For more information, refer to [Live instant clipping](/stream/stream-live/live-instant-clipping/) documentation.
|
||||
- publish_date: '2024-02-16'
|
||||
title: Tonemapping improvements for HDR content
|
||||
description: |-
|
||||
In certain cases, videos uploaded with an HDR colorspace (such as footage from certain mobile devices) appeared washed out or desaturated when played back. This issue is resolved for new uploads.
|
||||
- publish_date: '2023-11-07'
|
||||
title: HLS improvements for on-demand TS output
|
||||
description: |-
|
||||
HLS output from Cloudflare Stream on-demand videos that use Transport Stream file format now includes a 10 second offset to timestamps. This will have no impact on most customers. A small percentage of customers will see improved playback stability. Caption files were also adjusted accordingly.
|
||||
- publish_date: '2023-10-10'
|
||||
title: SRT Audio Improvements
|
||||
description: |-
|
||||
In some cases, playback via SRT protocol was missing an audio track regardless of existence of audio in the broadcast. This issue is now resolved.
|
||||
- publish_date: '2023-09-25'
|
||||
title: LL-HLS Beta
|
||||
description: |-
|
||||
Low-Latency HTTP Live Streaming (LL-HLS) is now in open beta. Enable LL-HLS on your [live input](/stream/stream-live/start-stream-live/) for automatic low-latency playback using the Stream built-in player where supported.
|
||||
When creating/editing a notification, subscribe to `live_input.errored` to receive the new event type. Existing notification subscriptions will not be changed automatically. For more information, refer to [Receive Live Webhooks](/stream/stream-live/webhooks/).
|
||||
- publish_date: "2024-06-20"
|
||||
title: Generated Captions to Open beta
|
||||
description: |-
|
||||
Stream has introduced automatically generated captions to open beta for all subscribers at no additional cost. While in beta, only English is supported and videos must be less than 2 hours. For more information, refer to the [product announcement and deep dive](https://blog.cloudflare.com/stream-automatic-captions-with-ai) or refer to the [captions documentation](/stream/edit-videos/adding-captions/) to get started.
|
||||
- publish_date: "2024-06-11"
|
||||
title: Updated response codes on requests for errored videos
|
||||
description: |-
|
||||
Stream will now return HTTP error status 424 (failed dependency) when requesting segments, manifests, thumbnails, downloads, or subtitles for videos that are in an errored state. Previously, Stream would return one of several 5xx codes for requests like this.
|
||||
- publish_date: "2024-04-11"
|
||||
title: Live Instant Clipping for live broadcasts and recordings
|
||||
description: |-
|
||||
Clipping is now available in open beta for live broadcasts and recordings. For more information, refer to [Live instant clipping](/stream/stream-live/live-instant-clipping/) documentation.
|
||||
- publish_date: "2024-02-16"
|
||||
title: Tonemapping improvements for HDR content
|
||||
description: |-
|
||||
In certain cases, videos uploaded with an HDR colorspace (such as footage from certain mobile devices) appeared washed out or desaturated when played back. This issue is resolved for new uploads.
|
||||
- publish_date: "2023-11-07"
|
||||
title: HLS improvements for on-demand TS output
|
||||
description: |-
|
||||
HLS output from Cloudflare Stream on-demand videos that use Transport Stream file format now includes a 10 second offset to timestamps. This will have no impact on most customers. A small percentage of customers will see improved playback stability. Caption files were also adjusted accordingly.
|
||||
- publish_date: "2023-10-10"
|
||||
title: SRT Audio Improvements
|
||||
description: |-
|
||||
In some cases, playback via SRT protocol was missing an audio track regardless of existence of audio in the broadcast. This issue is now resolved.
|
||||
- publish_date: "2023-09-25"
|
||||
title: LL-HLS Beta
|
||||
description: |-
|
||||
Low-Latency HTTP Live Streaming (LL-HLS) is now in open beta. Enable LL-HLS on your [live input](/stream/stream-live/start-stream-live/) for automatic low-latency playback using the Stream built-in player where supported.
|
||||
|
||||
For more information, refer to [live input](/stream/stream-live/start-stream-live/) and [custom player](/stream/viewing-videos/using-own-player/) docs.
|
||||
- publish_date: '2023-08-08'
|
||||
title: Scheduled Deletion
|
||||
description: |-
|
||||
Stream now supports adding a scheduled deletion date to new and existing videos. Live inputs support deletion policies for automatic recording deletion.
|
||||
For more information, refer to [live input](/stream/stream-live/start-stream-live/) and [custom player](/stream/viewing-videos/using-own-player/) docs.
|
||||
- publish_date: "2023-08-08"
|
||||
title: Scheduled Deletion
|
||||
description: |-
|
||||
Stream now supports adding a scheduled deletion date to new and existing videos. Live inputs support deletion policies for automatic recording deletion.
|
||||
|
||||
For more, refer to the [video on demand](/stream/uploading-videos/) or [live input](/stream/stream-live/) docs.
|
||||
- publish_date: '2023-05-16'
|
||||
title: Multiple audio tracks now generally available
|
||||
description: |-
|
||||
Stream supports adding multiple audio tracks to an existing video.
|
||||
For more, refer to the [video on demand](/stream/uploading-videos/) or [live input](/stream/stream-live/) docs.
|
||||
- publish_date: "2023-05-16"
|
||||
title: Multiple audio tracks now generally available
|
||||
description: |-
|
||||
Stream supports adding multiple audio tracks to an existing video.
|
||||
|
||||
For more, refer to the [documentation](https://developers.cloudflare.com/stream/edit-videos/adding-additional-audio-tracks/) to get started.
|
||||
- publish_date: '2023-04-26'
|
||||
title: Player Enhancement Properties
|
||||
description: |-
|
||||
Cloudflare Stream now supports player enhancement properties.
|
||||
For more, refer to the [documentation](https://developers.cloudflare.com/stream/edit-videos/adding-additional-audio-tracks/) to get started.
|
||||
- publish_date: "2023-04-26"
|
||||
title: Player Enhancement Properties
|
||||
description: |-
|
||||
Cloudflare Stream now supports player enhancement properties.
|
||||
|
||||
With player enhancements, you can modify your video player to incorporate elements of your branding, such as your logo, and customize additional options to present to your viewers.
|
||||
With player enhancements, you can modify your video player to incorporate elements of your branding, such as your logo, and customize additional options to present to your viewers.
|
||||
|
||||
For more, refer to the [documentation](https://developers.cloudflare.com/stream/edit-videos/player-enhancements/) to get started.
|
||||
- publish_date: '2023-03-21'
|
||||
title: Limits for downloadable MP4s for live recordings
|
||||
description: |-
|
||||
Previously, generating a download for a live recording exceeding four hours resulted in failure.
|
||||
For more, refer to the [documentation](https://developers.cloudflare.com/stream/edit-videos/player-enhancements/) to get started.
|
||||
- publish_date: "2023-03-21"
|
||||
title: Limits for downloadable MP4s for live recordings
|
||||
description: |-
|
||||
Previously, generating a download for a live recording exceeding four hours resulted in failure.
|
||||
|
||||
To fix the issue, now video downloads are only available for live recordings under four hours. Live recordings exceeding four hours can still be played but cannot be downloaded.
|
||||
- publish_date: '2023-01-04'
|
||||
title: Earlier detection (and rejection) of non-video uploads
|
||||
description: |-
|
||||
Cloudflare Stream now detects non-video content on upload using [the POST API](/stream/uploading-videos/upload-video-file/) and returns a 400 Bad Request HTTP error with code `10059`.
|
||||
To fix the issue, now video downloads are only available for live recordings under four hours. Live recordings exceeding four hours can still be played but cannot be downloaded.
|
||||
- publish_date: "2023-01-04"
|
||||
title: Earlier detection (and rejection) of non-video uploads
|
||||
description: |-
|
||||
Cloudflare Stream now detects non-video content on upload using [the POST API](/stream/uploading-videos/upload-video-file/) and returns a 400 Bad Request HTTP error with code `10059`.
|
||||
|
||||
Previously, if you or one of your users attempted to upload a file that is not a video (ex: an image), the request to upload would appear successful, but then fail to be encoded later on.
|
||||
Previously, if you or one of your users attempted to upload a file that is not a video (ex: an image), the request to upload would appear successful, but then fail to be encoded later on.
|
||||
|
||||
With this change, Stream responds to the upload request with an error, allowing you to give users immediate feedback if they attempt to upload non-video content.
|
||||
- publish_date: '2022-12-08'
|
||||
title: Faster mp4 downloads of live recordings
|
||||
description: Generating MP4 downloads of live stream recordings is now significantly
|
||||
faster. For more, refer to [the docs](/stream/stream-live/download-stream-live-videos/).
|
||||
- publish_date: '2022-11-29'
|
||||
title: Multiple audio tracks (closed beta)
|
||||
description: |-
|
||||
Stream now supports adding multiple audio tracks to an existing video upload. This allows you to:
|
||||
With this change, Stream responds to the upload request with an error, allowing you to give users immediate feedback if they attempt to upload non-video content.
|
||||
- publish_date: "2022-12-08"
|
||||
title: Faster mp4 downloads of live recordings
|
||||
description:
|
||||
Generating MP4 downloads of live stream recordings is now significantly
|
||||
faster. For more, refer to [the docs](/stream/stream-live/download-stream-live-videos/).
|
||||
- publish_date: "2022-11-29"
|
||||
title: Multiple audio tracks (closed beta)
|
||||
description: |-
|
||||
Stream now supports adding multiple audio tracks to an existing video upload. This allows you to:
|
||||
|
||||
- Provide viewers with audio tracks in multiple languages
|
||||
- Provide dubbed audio tracks, or audio commentary tracks (ex: Director’s Commentary)
|
||||
- Allow your users to customize the customize the audio mix, by providing separate audio tracks for music, speech or other audio tracks.
|
||||
- Provide Audio Description tracks to ensure your content is accessible. ([WCAG 2.0 Guideline 1.2 1](https://www.w3.org/TR/WCAG20/#media-equiv-audio-desc-only))
|
||||
- Provide viewers with audio tracks in multiple languages
|
||||
- Provide dubbed audio tracks, or audio commentary tracks (ex: Director’s Commentary)
|
||||
- Allow your users to customize the customize the audio mix, by providing separate audio tracks for music, speech or other audio tracks.
|
||||
- Provide Audio Description tracks to ensure your content is accessible. ([WCAG 2.0 Guideline 1.2 1](https://www.w3.org/TR/WCAG20/#media-equiv-audio-desc-only))
|
||||
|
||||
To request an invite to the beta, refer to [this post](https://community.cloudflare.com/t/new-in-beta-support-for-multiple-audio-tracks/439629).
|
||||
- publish_date: '2022-11-22'
|
||||
title: VP9 support for WebRTC live streams (beta)
|
||||
description: Cloudflare Stream now supports [VP9](https://developers.google.com/media/vp9)
|
||||
when streaming using [WebRTC (WHIP)](/stream/webrtc-beta/), currently in beta.
|
||||
- publish_date: '2022-11-08'
|
||||
title: Reduced time to start WebRTC streaming and playback with Trickle ICE
|
||||
description: |-
|
||||
Cloudflare Stream's [WHIP](https://datatracker.ietf.org/doc/draft-ietf-wish-whip/) and [WHEP](https://www.ietf.org/archive/id/draft-murillo-whep-01.html) implementations now support [Trickle ICE](https://datatracker.ietf.org/doc/rfc8838/), reducing the time it takes to initialize WebRTC connections, and increasing compatibility with WHIP and WHEP clients.
|
||||
To request an invite to the beta, refer to [this post](https://community.cloudflare.com/t/new-in-beta-support-for-multiple-audio-tracks/439629).
|
||||
- publish_date: "2022-11-22"
|
||||
title: VP9 support for WebRTC live streams (beta)
|
||||
description:
|
||||
Cloudflare Stream now supports [VP9](https://developers.google.com/media/vp9)
|
||||
when streaming using [WebRTC (WHIP)](/stream/webrtc-beta/), currently in beta.
|
||||
- publish_date: "2022-11-08"
|
||||
title: Reduced time to start WebRTC streaming and playback with Trickle ICE
|
||||
description: |-
|
||||
Cloudflare Stream's [WHIP](https://datatracker.ietf.org/doc/draft-ietf-wish-whip/) and [WHEP](https://www.ietf.org/archive/id/draft-murillo-whep-01.html) implementations now support [Trickle ICE](https://datatracker.ietf.org/doc/rfc8838/), reducing the time it takes to initialize WebRTC connections, and increasing compatibility with WHIP and WHEP clients.
|
||||
|
||||
For more, refer to [the docs](/stream/webrtc-beta/).
|
||||
- publish_date: '2022-11-07'
|
||||
title: Deprecating the 'per-video' Analytics API
|
||||
description: |-
|
||||
The “per-video” analytics API is being deprecated. If you still use this API, you will need to switch to using the [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics/) by February 1, 2023. After this date, the per-video analytics API will be no longer available.
|
||||
For more, refer to [the docs](/stream/webrtc-beta/).
|
||||
- publish_date: "2022-11-07"
|
||||
title: Deprecating the 'per-video' Analytics API
|
||||
description: |-
|
||||
The “per-video” analytics API is being deprecated. If you still use this API, you will need to switch to using the [GraphQL Analytics API](/stream/getting-analytics/fetching-bulk-analytics/) by February 1, 2023. After this date, the per-video analytics API will be no longer available.
|
||||
|
||||
The GraphQL Analytics API provides the same functionality and more, with additional filters and metrics, as well as the ability to fetch data about multiple videos in a single request. Queries are faster, more reliable, and built on a shared analytics system that you can [use across many Cloudflare products](/analytics/graphql-api/features/data-sets/).
|
||||
The GraphQL Analytics API provides the same functionality and more, with additional filters and metrics, as well as the ability to fetch data about multiple videos in a single request. Queries are faster, more reliable, and built on a shared analytics system that you can [use across many Cloudflare products](/analytics/graphql-api/features/data-sets/).
|
||||
|
||||
For more about this change and how to migrate existing API queries, refer to [this post](https://community.cloudflare.com/t/migrate-to-the-stream-graphql-analytics-api-by-feb-1st-2023/433252) and the [GraphQL Analytics API docs](/stream/getting-analytics/fetching-bulk-analytics/).
|
||||
- publish_date: '2022-11-01'
|
||||
title: Create an unlimited number of live inputs
|
||||
description: |-
|
||||
Cloudflare Stream now has no limit on the number of [live inputs](/api/operations/stream-live-inputs-retrieve-a-live-input) you can create. Stream is designed to allow your end-users to go live — live inputs can be created quickly on-demand via a single API request for each of user of your platform or app.
|
||||
For more about this change and how to migrate existing API queries, refer to [this post](https://community.cloudflare.com/t/migrate-to-the-stream-graphql-analytics-api-by-feb-1st-2023/433252) and the [GraphQL Analytics API docs](/stream/getting-analytics/fetching-bulk-analytics/).
|
||||
- publish_date: "2022-11-01"
|
||||
title: Create an unlimited number of live inputs
|
||||
description: |-
|
||||
Cloudflare Stream now has no limit on the number of [live inputs](/api/operations/stream-live-inputs-retrieve-a-live-input) you can create. Stream is designed to allow your end-users to go live — live inputs can be created quickly on-demand via a single API request for each of user of your platform or app.
|
||||
|
||||
For more on creating and managing live inputs, get started with the [docs](/stream/stream-live/).
|
||||
- publish_date: '2022-10-20'
|
||||
title: More accurate bandwidth estimates for live video playback
|
||||
description: |-
|
||||
When playing live video, Cloudflare Stream now provides significantly more accurate estimates of the bandwidth needs of each quality level to client video players. This ensures that live video plays at the highest quality that viewers have adequate bandwidth to play.
|
||||
For more on creating and managing live inputs, get started with the [docs](/stream/stream-live/).
|
||||
- publish_date: "2022-10-20"
|
||||
title: More accurate bandwidth estimates for live video playback
|
||||
description: |-
|
||||
When playing live video, Cloudflare Stream now provides significantly more accurate estimates of the bandwidth needs of each quality level to client video players. This ensures that live video plays at the highest quality that viewers have adequate bandwidth to play.
|
||||
|
||||
As live video is streamed to Cloudflare, we transcode it to make it available to viewers at multiple quality levels. During transcoding, we learn about the real bandwidth needs of each segment of video at each quality level, and use this to provide an estimate of the bandwidth requirements of each quality level the in HLS (`.m3u8`) and DASH (`.mpd`) manifests.
|
||||
As live video is streamed to Cloudflare, we transcode it to make it available to viewers at multiple quality levels. During transcoding, we learn about the real bandwidth needs of each segment of video at each quality level, and use this to provide an estimate of the bandwidth requirements of each quality level the in HLS (`.m3u8`) and DASH (`.mpd`) manifests.
|
||||
|
||||
If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS manifest will be lower, ensuring that the most viewers possible view the highest quality level, since it requires relatively little bandwidth. Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the HLS manifest will be higher, ensuring that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
|
||||
If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS manifest will be lower, ensuring that the most viewers possible view the highest quality level, since it requires relatively little bandwidth. Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the HLS manifest will be higher, ensuring that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.
|
||||
|
||||
This change is particularly helpful if you're building a platform or application that allows your end users to create their own live streams, where these end users have their own streaming software and hardware that you can't control. Because this new functionality adapts based on the live video we receive, rather than just the configuration advertised by the broadcaster, even in cases where your end users' settings are less than ideal, client video players will not receive excessively high estimates of bandwidth requirements, causing playback quality to decrease unnecessarily. Your end users don't have to be OBS Studio experts in order to get high quality video playback.
|
||||
This change is particularly helpful if you're building a platform or application that allows your end users to create their own live streams, where these end users have their own streaming software and hardware that you can't control. Because this new functionality adapts based on the live video we receive, rather than just the configuration advertised by the broadcaster, even in cases where your end users' settings are less than ideal, client video players will not receive excessively high estimates of bandwidth requirements, causing playback quality to decrease unnecessarily. Your end users don't have to be OBS Studio experts in order to get high quality video playback.
|
||||
|
||||
No work is required on your end — this change applies to all live inputs, for all customers of Cloudflare Stream. For more, refer to the [docs](/stream/stream-live/#bitrate-estimates-at-each-quality-level-bitrate-ladder).
|
||||
- publish_date: '2022-10-05'
|
||||
title: AV1 Codec support for live streams and recordings (beta)
|
||||
description: |-
|
||||
Cloudflare Stream now supports playback of live videos and live recordings using the [AV1 codec](https://aomedia.org/av1/), which uses 46% less bandwidth than H.264.
|
||||
No work is required on your end — this change applies to all live inputs, for all customers of Cloudflare Stream. For more, refer to the [docs](/stream/stream-live/#bitrate-estimates-at-each-quality-level-bitrate-ladder).
|
||||
- publish_date: "2022-10-05"
|
||||
title: AV1 Codec support for live streams and recordings (beta)
|
||||
description: |-
|
||||
Cloudflare Stream now supports playback of live videos and live recordings using the [AV1 codec](https://aomedia.org/av1/), which uses 46% less bandwidth than H.264.
|
||||
|
||||
For more, read the [blog post](https://blog.cloudflare.com/av1-cloudflare-stream-beta).
|
||||
- publish_date: '2022-09-27'
|
||||
title: WebRTC live streaming and playback (beta)
|
||||
description: |-
|
||||
Cloudflare Stream now supports live video streaming over WebRTC, with sub-second latency, to unlimited concurrent viewers.
|
||||
For more, read the [blog post](https://blog.cloudflare.com/av1-cloudflare-stream-beta).
|
||||
- publish_date: "2022-09-27"
|
||||
title: WebRTC live streaming and playback (beta)
|
||||
description: |-
|
||||
Cloudflare Stream now supports live video streaming over WebRTC, with sub-second latency, to unlimited concurrent viewers.
|
||||
|
||||
For more, read the [blog post](https://blog.cloudflare.com/webrtc-whip-whep-cloudflare-stream) or the get started with example code in the [docs](/stream/webrtc-beta).
|
||||
- publish_date: '2022-09-15'
|
||||
title: Manually control when you start and stop simulcasting
|
||||
description: You can now enable and disable individual live outputs via the API
|
||||
or Stream dashboard, allowing you to control precisely when you start and stop
|
||||
simulcasting to specific destinations like YouTube and Twitch. For more, [read
|
||||
the docs](/stream/stream-live/simulcasting/#control-when-you-start-and-stop-simulcasting).
|
||||
- publish_date: '2022-08-15'
|
||||
title: Unique subdomain for your Stream Account
|
||||
description: |-
|
||||
URLs in the Stream Dashboard and Stream API now use a subdomain specific to your Cloudflare Account: `customer-{CODE}.cloudflarestream.com`. This change allows you to:
|
||||
For more, read the [blog post](https://blog.cloudflare.com/webrtc-whip-whep-cloudflare-stream) or the get started with example code in the [docs](/stream/webrtc-beta).
|
||||
- publish_date: "2022-09-15"
|
||||
title: Manually control when you start and stop simulcasting
|
||||
description:
|
||||
You can now enable and disable individual live outputs via the API
|
||||
or Stream dashboard, allowing you to control precisely when you start and stop
|
||||
simulcasting to specific destinations like YouTube and Twitch. For more, [read
|
||||
the docs](/stream/stream-live/simulcasting/#control-when-you-start-and-stop-simulcasting).
|
||||
- publish_date: "2022-08-15"
|
||||
title: Unique subdomain for your Stream Account
|
||||
description: |-
|
||||
URLs in the Stream Dashboard and Stream API now use a subdomain specific to your Cloudflare Account: `customer-{CODE}.cloudflarestream.com`. This change allows you to:
|
||||
|
||||
1. Use [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) (CSP) directives specific to your Stream subdomain, to ensure that only videos from your Cloudflare account can be played on your website.
|
||||
1. Use [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) (CSP) directives specific to your Stream subdomain, to ensure that only videos from your Cloudflare account can be played on your website.
|
||||
|
||||
2. Allowlist only your Stream account subdomain at the network-level to ensure that only videos from a specific Cloudflare account can be accessed on your network.
|
||||
2. Allowlist only your Stream account subdomain at the network-level to ensure that only videos from a specific Cloudflare account can be accessed on your network.
|
||||
|
||||
No action is required from you, unless you use Content Security Policy (CSP) on your website. For more on CSP, read the [docs](/stream/faq/#i-use-content-security-policy-csp-on-my-website-what-domains-do-i-need-to-add-to-which-directives).
|
||||
- publish_date: '2022-08-02'
|
||||
title: Clip videos using the Stream API
|
||||
description: You can now change the start and end times of a video uploaded to Cloudflare
|
||||
Stream. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
|
||||
- publish_date: '2022-07-26'
|
||||
title: Live inputs
|
||||
description: The Live Inputs API now supports optional pagination, search, and filter
|
||||
parameters. For more information, refer to the [Live Inputs API documentation](/api/operations/stream-live-inputs-list-live-inputs).
|
||||
- publish_date: '2022-05-24'
|
||||
title: Picture-in-Picture support
|
||||
description: The [Stream Player](/stream/viewing-videos/using-the-stream-player/)
|
||||
now displays a button to activate Picture-in-Picture mode, if the viewer's web
|
||||
browser supports the [Picture-in-Picture API](https://developer.mozilla.org/en-US/docs/Web/API/Picture-in-Picture_API).
|
||||
- publish_date: '2022-05-13'
|
||||
title: Creator ID property
|
||||
description: During or after uploading a video to Stream, you can now specify a
|
||||
value for a new field, `creator`. This field can be used to identify the creator
|
||||
of the video content, linking the way you identify your users or creators to videos
|
||||
in your Stream account. For more, read the [blog post](https://blog.cloudflare.com/stream-creator-management/).
|
||||
- publish_date: '2022-03-17'
|
||||
title: Analytics panel in Stream Dashboard
|
||||
description: The Stream Dashboard now has an analytics panel that shows the number
|
||||
of minutes of both live and recorded video delivered. This view can be filtered
|
||||
by **Creator ID**, **Video UID**, and **Country**. For more in-depth analytics
|
||||
data, refer to the [bulk analytics documentation](/stream/getting-analytics/fetching-bulk-analytics/).
|
||||
- publish_date: '2022-03-16'
|
||||
title: Custom letterbox color configuration option for Stream Player
|
||||
description: The Stream Player can now be configured to use a custom letterbox color,
|
||||
displayed around the video ('letterboxing' or 'pillarboxing') when the video's
|
||||
aspect ratio does not match the player's aspect ratio. Refer to the documentation
|
||||
on configuring the Stream Player [here](/stream/viewing-videos/using-the-stream-player/#basic-options).
|
||||
- publish_date: '2022-03-10'
|
||||
title: Support for SRT live streaming protocol
|
||||
description: |-
|
||||
Cloudflare Stream now supports the SRT live streaming protocol. SRT is a modern, actively maintained streaming video protocol that delivers lower latency, and better resilience against unpredictable network conditions. SRT supports newer video codecs and makes it easier to use accessibility features such as captions and multiple audio tracks.
|
||||
No action is required from you, unless you use Content Security Policy (CSP) on your website. For more on CSP, read the [docs](/stream/faq/#i-use-content-security-policy-csp-on-my-website-what-domains-do-i-need-to-add-to-which-directives).
|
||||
- publish_date: "2022-08-02"
|
||||
title: Clip videos using the Stream API
|
||||
description:
|
||||
You can now change the start and end times of a video uploaded to Cloudflare
|
||||
Stream. For more information, refer to [Clip videos](/stream/edit-videos/video-clipping/).
|
||||
- publish_date: "2022-07-26"
|
||||
title: Live inputs
|
||||
description:
|
||||
The Live Inputs API now supports optional pagination, search, and filter
|
||||
parameters. For more information, refer to the [Live Inputs API documentation](/api/operations/stream-live-inputs-list-live-inputs).
|
||||
- publish_date: "2022-05-24"
|
||||
title: Picture-in-Picture support
|
||||
description:
|
||||
The [Stream Player](/stream/viewing-videos/using-the-stream-player/)
|
||||
now displays a button to activate Picture-in-Picture mode, if the viewer's web
|
||||
browser supports the [Picture-in-Picture API](https://developer.mozilla.org/en-US/docs/Web/API/Picture-in-Picture_API).
|
||||
- publish_date: "2022-05-13"
|
||||
title: Creator ID property
|
||||
description:
|
||||
During or after uploading a video to Stream, you can now specify a
|
||||
value for a new field, `creator`. This field can be used to identify the creator
|
||||
of the video content, linking the way you identify your users or creators to videos
|
||||
in your Stream account. For more, read the [blog post](https://blog.cloudflare.com/stream-creator-management/).
|
||||
- publish_date: "2022-03-17"
|
||||
title: Analytics panel in Stream Dashboard
|
||||
description:
|
||||
The Stream Dashboard now has an analytics panel that shows the number
|
||||
of minutes of both live and recorded video delivered. This view can be filtered
|
||||
by **Creator ID**, **Video UID**, and **Country**. For more in-depth analytics
|
||||
data, refer to the [bulk analytics documentation](/stream/getting-analytics/fetching-bulk-analytics/).
|
||||
- publish_date: "2022-03-16"
|
||||
title: Custom letterbox color configuration option for Stream Player
|
||||
description:
|
||||
The Stream Player can now be configured to use a custom letterbox color,
|
||||
displayed around the video ('letterboxing' or 'pillarboxing') when the video's
|
||||
aspect ratio does not match the player's aspect ratio. Refer to the documentation
|
||||
on configuring the Stream Player [here](/stream/viewing-videos/using-the-stream-player/#basic-options).
|
||||
- publish_date: "2022-03-10"
|
||||
title: Support for SRT live streaming protocol
|
||||
description: |-
|
||||
Cloudflare Stream now supports the SRT live streaming protocol. SRT is a modern, actively maintained streaming video protocol that delivers lower latency, and better resilience against unpredictable network conditions. SRT supports newer video codecs and makes it easier to use accessibility features such as captions and multiple audio tracks.
|
||||
|
||||
For more, read the [blog post](https://blog.cloudflare.com/stream-now-supports-srt-as-a-drop-in-replacement-for-rtmp/).
|
||||
- publish_date: '2022-02-17'
|
||||
title: Faster video quality switching in Stream Player
|
||||
description: When viewers manually change the resolution of video they want to receive
|
||||
in the Stream Player, this change now happens immediately, rather than once the
|
||||
existing resolution playback buffer has finished playing.
|
||||
- publish_date: '2022-02-09'
|
||||
title: Volume and playback controls accessible during playback of VAST Ads
|
||||
description: When viewing ads in the [VAST format](https://www.iab.com/guidelines/vast/#:~:text=VAST%20is%20a%20Video%20Ad,of%20the%20digital%20video%20marketplace.)
|
||||
in the Stream Player, viewers can now manually start and stop the video, or control
|
||||
the volume.
|
||||
- publish_date: '2022-01-25'
|
||||
title: DASH and HLS manifest URLs accessible in Stream Dashboard
|
||||
description: If you choose to use a third-party player with Cloudflare Stream, you
|
||||
can now easily access HLS and DASH manifest URLs from within the Stream Dashboard.
|
||||
For more about using Stream with third-party players, read the docs [here](/stream/viewing-videos/using-own-player/).
|
||||
- publish_date: '2022-01-22'
|
||||
title: Input health status in the Stream Dashboard
|
||||
description: When a live input is connected, the Stream Dashboard now displays technical
|
||||
details about the connection, which can be used to debug configuration issues.
|
||||
- publish_date: '2022-01-06'
|
||||
title: Live viewer count in the Stream Player
|
||||
description: The [Stream Player](/stream/viewing-videos/using-the-stream-player/)
|
||||
now shows the total number of people currently watching a video live.
|
||||
- publish_date: '2022-01-04'
|
||||
title: Webhook notifications for live stream connections events
|
||||
description: You can now configure Stream to send webhooks each time a live stream
|
||||
connects and disconnects. For more information, refer to the [Webhooks documentation](/stream/stream-live/webhooks).
|
||||
- publish_date: '2021-12-07'
|
||||
title: FedRAMP Support
|
||||
description: The Stream Player can now be served from a [FedRAMP](https://www.cloudflare.com/press-releases/2021/cloudflare-hits-milestone-in-fedramp-approval/)
|
||||
compliant subdomain.
|
||||
- publish_date: '2021-11-23'
|
||||
title: 24/7 Live streaming support
|
||||
description: You can now use Cloudflare Stream for 24/7 live streaming.
|
||||
- publish_date: '2021-11-17'
|
||||
title: Persistent Live Stream IDs
|
||||
description: You can now start and stop live broadcasts without having to provide
|
||||
a new video UID to the Stream Player (or your own player) each time the stream
|
||||
starts and stops. [Read the docs](/stream/stream-live/watch-live-stream/#view-by-live-input-id).
|
||||
- publish_date: '2021-10-14'
|
||||
title: MP4 video file downloads for live videos
|
||||
description: Once a live video has ended and been recorded, you can now give viewers
|
||||
the option to download an MP4 video file of the live recording. For more, read
|
||||
the docs [here](/stream/stream-live/download-stream-live-videos/).
|
||||
- publish_date: '2021-09-30'
|
||||
title: Serverless Live Streaming
|
||||
description: Stream now supports live video content! For more information, read
|
||||
the [blog post](https://blog.cloudflare.com/stream-live/) and get started by reading
|
||||
the [docs](/stream/stream-live/).
|
||||
- publish_date: '2021-07-26'
|
||||
title: Thumbnail previews in Stream Player seek bar
|
||||
description: The Stream Player now displays preview images when viewers hover their
|
||||
mouse over the seek bar, making it easier to skip to a specific part of a video.
|
||||
- publish_date: '2021-07-26'
|
||||
title: MP4 video file downloads (GA)
|
||||
description: All Cloudflare Stream customers can now give viewers the option to
|
||||
download videos uploaded to Stream as an MP4 video file. For more, read the docs
|
||||
[here](/stream/viewing-videos/download-videos/).
|
||||
- publish_date: '2021-07-10'
|
||||
title: Stream Connect (open beta)
|
||||
description: |-
|
||||
You can now opt-in to the Stream Connect beta, and use Cloudflare Stream to restream live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.
|
||||
For more, read the [blog post](https://blog.cloudflare.com/stream-now-supports-srt-as-a-drop-in-replacement-for-rtmp/).
|
||||
- publish_date: "2022-02-17"
|
||||
title: Faster video quality switching in Stream Player
|
||||
description:
|
||||
When viewers manually change the resolution of video they want to receive
|
||||
in the Stream Player, this change now happens immediately, rather than once the
|
||||
existing resolution playback buffer has finished playing.
|
||||
- publish_date: "2022-02-09"
|
||||
title: Volume and playback controls accessible during playback of VAST Ads
|
||||
description:
|
||||
When viewing ads in the [VAST format](https://www.iab.com/guidelines/vast/#:~:text=VAST%20is%20a%20Video%20Ad,of%20the%20digital%20video%20marketplace.)
|
||||
in the Stream Player, viewers can now manually start and stop the video, or control
|
||||
the volume.
|
||||
- publish_date: "2022-01-25"
|
||||
title: DASH and HLS manifest URLs accessible in Stream Dashboard
|
||||
description:
|
||||
If you choose to use a third-party player with Cloudflare Stream, you
|
||||
can now easily access HLS and DASH manifest URLs from within the Stream Dashboard.
|
||||
For more about using Stream with third-party players, read the docs [here](/stream/viewing-videos/using-own-player/).
|
||||
- publish_date: "2022-01-22"
|
||||
title: Input health status in the Stream Dashboard
|
||||
description:
|
||||
When a live input is connected, the Stream Dashboard now displays technical
|
||||
details about the connection, which can be used to debug configuration issues.
|
||||
- publish_date: "2022-01-06"
|
||||
title: Live viewer count in the Stream Player
|
||||
description:
|
||||
The [Stream Player](/stream/viewing-videos/using-the-stream-player/)
|
||||
now shows the total number of people currently watching a video live.
|
||||
- publish_date: "2022-01-04"
|
||||
title: Webhook notifications for live stream connections events
|
||||
description:
|
||||
You can now configure Stream to send webhooks each time a live stream
|
||||
connects and disconnects. For more information, refer to the [Webhooks documentation](/stream/stream-live/webhooks).
|
||||
- publish_date: "2021-12-07"
|
||||
title: FedRAMP Support
|
||||
description:
|
||||
The Stream Player can now be served from a [FedRAMP](https://www.cloudflare.com/press-releases/2021/cloudflare-hits-milestone-in-fedramp-approval/)
|
||||
compliant subdomain.
|
||||
- publish_date: "2021-11-23"
|
||||
title: 24/7 Live streaming support
|
||||
description: You can now use Cloudflare Stream for 24/7 live streaming.
|
||||
- publish_date: "2021-11-17"
|
||||
title: Persistent Live Stream IDs
|
||||
description:
|
||||
You can now start and stop live broadcasts without having to provide
|
||||
a new video UID to the Stream Player (or your own player) each time the stream
|
||||
starts and stops. [Read the docs](/stream/stream-live/watch-live-stream/#view-by-live-input-id).
|
||||
- publish_date: "2021-10-14"
|
||||
title: MP4 video file downloads for live videos
|
||||
description:
|
||||
Once a live video has ended and been recorded, you can now give viewers
|
||||
the option to download an MP4 video file of the live recording. For more, read
|
||||
the docs [here](/stream/stream-live/download-stream-live-videos/).
|
||||
- publish_date: "2021-09-30"
|
||||
title: Serverless Live Streaming
|
||||
description:
|
||||
Stream now supports live video content! For more information, read
|
||||
the [blog post](https://blog.cloudflare.com/stream-live/) and get started by reading
|
||||
the [docs](/stream/stream-live/).
|
||||
- publish_date: "2021-07-26"
|
||||
title: Thumbnail previews in Stream Player seek bar
|
||||
description:
|
||||
The Stream Player now displays preview images when viewers hover their
|
||||
mouse over the seek bar, making it easier to skip to a specific part of a video.
|
||||
- publish_date: "2021-07-26"
|
||||
title: MP4 video file downloads (GA)
|
||||
description:
|
||||
All Cloudflare Stream customers can now give viewers the option to
|
||||
download videos uploaded to Stream as an MP4 video file. For more, read the docs
|
||||
[here](/stream/viewing-videos/download-videos/).
|
||||
- publish_date: "2021-07-10"
|
||||
title: Stream Connect (open beta)
|
||||
description: |-
|
||||
You can now opt-in to the Stream Connect beta, and use Cloudflare Stream to restream live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.
|
||||
|
||||
For more, read the [blog post](https://blog.cloudflare.com/restream-with-stream-connect/) or the [docs](/stream/stream-live/simulcasting/).
|
||||
- publish_date: '2021-06-10'
|
||||
title: Simplified signed URL token generation
|
||||
description: You can now obtain a signed URL token via a single API request, without
|
||||
needing to generate signed tokens in your own application. [Read the docs](/stream/viewing-videos/securing-your-stream).
|
||||
- publish_date: '2021-06-08'
|
||||
title: Stream Connect (closed beta)
|
||||
description: |-
|
||||
You can now use Cloudflare Stream to restream or simulcast live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.
|
||||
For more, read the [blog post](https://blog.cloudflare.com/restream-with-stream-connect/) or the [docs](/stream/stream-live/simulcasting/).
|
||||
- publish_date: "2021-06-10"
|
||||
title: Simplified signed URL token generation
|
||||
description:
|
||||
You can now obtain a signed URL token via a single API request, without
|
||||
needing to generate signed tokens in your own application. [Read the docs](/stream/viewing-videos/securing-your-stream).
|
||||
- publish_date: "2021-06-08"
|
||||
title: Stream Connect (closed beta)
|
||||
description: |-
|
||||
You can now use Cloudflare Stream to restream or simulcast live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.
|
||||
|
||||
For more, read the [blog post](https://blog.cloudflare.com/restream-with-stream-connect/) or the [docs](/stream/stream-live/simulcasting/).
|
||||
- publish_date: '2021-05-03'
|
||||
title: MP4 video file downloads (beta)
|
||||
description: You can now give your viewers the option to download videos uploaded
|
||||
to Stream as an MP4 video file. For more, read the docs [here](/stream/viewing-videos/download-videos/).
|
||||
- publish_date: '2021-03-25'
|
||||
title: Improved client bandwidth hints for third-party video players
|
||||
description: If you use Cloudflare Stream with a third party player, and send the `clientBandwidthHint` parameter in requests to fetch video manifests, Cloudflare Stream now selects the ideal resolution to provide to your client player more intelligently. This ensures your viewers receive the ideal resolution for their network connection.
|
||||
- publish_date: '2021-03-10'
|
||||
title: Stream Player 2.0 (preview)
|
||||
description: |-
|
||||
A brand new version of the Stream Player is now available for preview. New features include:
|
||||
For more, read the [blog post](https://blog.cloudflare.com/restream-with-stream-connect/) or the [docs](/stream/stream-live/simulcasting/).
|
||||
- publish_date: "2021-05-03"
|
||||
title: MP4 video file downloads (beta)
|
||||
description:
|
||||
You can now give your viewers the option to download videos uploaded
|
||||
to Stream as an MP4 video file. For more, read the docs [here](/stream/viewing-videos/download-videos/).
|
||||
- publish_date: "2021-03-25"
|
||||
title: Improved client bandwidth hints for third-party video players
|
||||
description: If you use Cloudflare Stream with a third party player, and send the `clientBandwidthHint` parameter in requests to fetch video manifests, Cloudflare Stream now selects the ideal resolution to provide to your client player more intelligently. This ensures your viewers receive the ideal resolution for their network connection.
|
||||
- publish_date: "2021-03-10"
|
||||
title: Stream Player 2.0 (preview)
|
||||
description: |-
|
||||
A brand new version of the Stream Player is now available for preview. New features include:
|
||||
|
||||
- Unified controls across desktop and mobile devices
|
||||
- Keyboard shortcuts
|
||||
- Intelligent mouse cursor interactions with player controls
|
||||
- Phased out support for Internet Explorer 11
|
||||
- Unified controls across desktop and mobile devices
|
||||
- Keyboard shortcuts
|
||||
- Intelligent mouse cursor interactions with player controls
|
||||
- Phased out support for Internet Explorer 11
|
||||
|
||||
For more, refer to [this post](https://community.cloudflare.com/t/announcing-the-preview-build-for-stream-player-2-0/243095) on the Cloudflare Community Forum.
|
||||
- publish_date: '2021-03-04'
|
||||
title: Faster video encoding
|
||||
description: Videos uploaded to Cloudflare Stream are now available to view 5x sooner,
|
||||
reducing the time your users wait between uploading and viewing videos.
|
||||
- publish_date: '2021-03-29'
|
||||
title: Picture quality improvements
|
||||
description: Cloudflare Stream now encodes videos with fewer artifacts, resulting
|
||||
in improved video quality for your viewers.
|
||||
- publish_date: '2021-03-25'
|
||||
title: Improved client bandwidth hints for third-party video players
|
||||
description: If you use Cloudflare Stream with a third party player, and send the
|
||||
`clientBandwidthHint` parameter in requests to fetch video manifests, Cloudflare
|
||||
Stream now selects the ideal resolution to provide to your client player more
|
||||
intelligently. This ensures your viewers receive the ideal resolution for their
|
||||
network connection.
|
||||
- publish_date: '2021-03-17'
|
||||
title: Less bandwidth, identical video quality
|
||||
description: Cloudflare Stream now delivers video using 3-10x less bandwidth, with
|
||||
no reduction in quality. This ensures faster playback for your viewers with less
|
||||
buffering, particularly when viewers have slower network connections.
|
||||
- publish_date: '2021-01-17'
|
||||
title: Removed weekly upload limit, increased max video upload size
|
||||
description: You can now upload videos up to 30GB in size to Cloudflare Stream and
|
||||
also now upload an unlimited number of videos to Cloudflare Stream each week
|
||||
- publish_date: '2020-12-14'
|
||||
title: Tus support for direct creator uploads
|
||||
description: |-
|
||||
You can now use the [tus protocol](/stream/uploading-videos/direct-creator-uploads/#advanced-upload-flow-using-tus-for-large-videos) when allowing creators (your end users) to upload their own videos directly to Cloudflare Stream.
|
||||
For more, refer to [this post](https://community.cloudflare.com/t/announcing-the-preview-build-for-stream-player-2-0/243095) on the Cloudflare Community Forum.
|
||||
- publish_date: "2021-03-04"
|
||||
title: Faster video encoding
|
||||
description:
|
||||
Videos uploaded to Cloudflare Stream are now available to view 5x sooner,
|
||||
reducing the time your users wait between uploading and viewing videos.
|
||||
- publish_date: "2021-03-29"
|
||||
title: Picture quality improvements
|
||||
description:
|
||||
Cloudflare Stream now encodes videos with fewer artifacts, resulting
|
||||
in improved video quality for your viewers.
|
||||
- publish_date: "2021-03-25"
|
||||
title: Improved client bandwidth hints for third-party video players
|
||||
description:
|
||||
If you use Cloudflare Stream with a third party player, and send the
|
||||
`clientBandwidthHint` parameter in requests to fetch video manifests, Cloudflare
|
||||
Stream now selects the ideal resolution to provide to your client player more
|
||||
intelligently. This ensures your viewers receive the ideal resolution for their
|
||||
network connection.
|
||||
- publish_date: "2021-03-17"
|
||||
title: Less bandwidth, identical video quality
|
||||
description:
|
||||
Cloudflare Stream now delivers video using 3-10x less bandwidth, with
|
||||
no reduction in quality. This ensures faster playback for your viewers with less
|
||||
buffering, particularly when viewers have slower network connections.
|
||||
- publish_date: "2021-01-17"
|
||||
title: Removed weekly upload limit, increased max video upload size
|
||||
description:
|
||||
You can now upload videos up to 30GB in size to Cloudflare Stream and
|
||||
also now upload an unlimited number of videos to Cloudflare Stream each week
|
||||
- publish_date: "2020-12-14"
|
||||
title: Tus support for direct creator uploads
|
||||
description: |-
|
||||
You can now use the [tus protocol](/stream/uploading-videos/direct-creator-uploads/#advanced-upload-flow-using-tus-for-large-videos) when allowing creators (your end users) to upload their own videos directly to Cloudflare Stream.
|
||||
|
||||
In addition, all uploads to Cloudflare Stream made using tus are now faster and more reliable as part of this change.
|
||||
- publish_date: '2020-12-09'
|
||||
title: Multiple audio track mixdown
|
||||
description: 'Videos with multiple audio tracks (ex: 5.1 surround sound) are now
|
||||
mixed down to stereo when uploaded to Stream. The resulting video, with stereo
|
||||
audio, is now playable in the Stream Player.'
|
||||
- publish_date: '2020-12-02'
|
||||
title: Storage limit notifications
|
||||
description: Cloudflare now emails you if your account is using 75% or more of your
|
||||
prepaid video storage, so that you can take action and plan ahead.
|
||||
In addition, all uploads to Cloudflare Stream made using tus are now faster and more reliable as part of this change.
|
||||
- publish_date: "2020-12-09"
|
||||
title: Multiple audio track mixdown
|
||||
description:
|
||||
"Videos with multiple audio tracks (ex: 5.1 surround sound) are now
|
||||
mixed down to stereo when uploaded to Stream. The resulting video, with stereo
|
||||
audio, is now playable in the Stream Player."
|
||||
- publish_date: "2020-12-02"
|
||||
title: Storage limit notifications
|
||||
description:
|
||||
Cloudflare now emails you if your account is using 75% or more of your
|
||||
prepaid video storage, so that you can take action and plan ahead.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/tenant/"
|
|||
productArea: Core platform
|
||||
productAreaLink: /fundamentals/reference/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2023-10-10'
|
||||
title: "New Tenant Admin UI"
|
||||
description: |-
|
||||
- Partners can now create and view accounts through the Cloudflare dashboard by going to **Tenants** > **Managed Accounts**.
|
||||
- publish_date: "2023-10-10"
|
||||
title: "New Tenant Admin UI"
|
||||
description: |-
|
||||
- Partners can now create and view accounts through the Cloudflare dashboard by going to **Tenants** > **Managed Accounts**.
|
||||
|
|
|
|||
|
|
@ -5,18 +5,17 @@ productLink: "/fundamentals/basic-tasks/trace-request/"
|
|||
productArea: Core platform
|
||||
productAreaLink: /fundamentals/reference/changelog/platform/
|
||||
entries:
|
||||
- publish_date: "2024-04-15"
|
||||
title: Cloudflare Trace now supports Workers
|
||||
description: |-
|
||||
Starting today, customers can use Cloudflare Trace to confirm if a request to a specific URL within their zone is routed through a [Workers script](/workers/).
|
||||
|
||||
- publish_date: '2024-04-15'
|
||||
title: Cloudflare Trace now supports Workers
|
||||
description: |-
|
||||
Starting today, customers can use Cloudflare Trace to confirm if a request to a specific URL within their zone is routed through a [Workers script](/workers/).
|
||||
- publish_date: "2024-03-18"
|
||||
title: Cloudflare Trace now supports BYOIP zones
|
||||
description: |-
|
||||
Customers can now use Cloudflare Trace to trace HTTP/S requests through their [BYOIP](/byoip/) zones.
|
||||
|
||||
- publish_date: '2024-03-18'
|
||||
title: Cloudflare Trace now supports BYOIP zones
|
||||
description: |-
|
||||
Customers can now use Cloudflare Trace to trace HTTP/S requests through their [BYOIP](/byoip/) zones.
|
||||
|
||||
- publish_date: '2024-03-12'
|
||||
title: Cloudflare Trace now supports grey-clouded hostnames
|
||||
description: |-
|
||||
Even if the hostname is [not proxied by Cloudflare](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.
|
||||
- publish_date: "2024-03-12"
|
||||
title: Cloudflare Trace now supports grey-clouded hostnames
|
||||
description: |-
|
||||
Even if the hostname is [not proxied by Cloudflare](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@ productLink: "/cloudflare-one/connections/connect-networks/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: '2024-09-10'
|
||||
title: Bugfix for --grace-period
|
||||
description: |-
|
||||
The new `cloudflared` build [2024.9.1](https://github.com/cloudflare/cloudflared/releases/tag/2024.9.0) has a bugfix related to the [--grace-period](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#grace-period) tunnel run parameter. `cloudflared` connectors will now abide by the specified waiting period before forcefully closing connections to Cloudflare's network.
|
||||
- publish_date: '2024-08-06'
|
||||
title: cloudflared builds available in GitHub for Apple silicon
|
||||
description: |-
|
||||
macOS users can now download `cloudflared-arm64.pkg` directly from [GitHub](https://github.com/cloudflare/cloudflared/releases), in addition to being available via Homebrew.
|
||||
- publish_date: "2024-09-10"
|
||||
title: Bugfix for --grace-period
|
||||
description: |-
|
||||
The new `cloudflared` build [2024.9.1](https://github.com/cloudflare/cloudflared/releases/tag/2024.9.0) has a bugfix related to the [--grace-period](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-run-parameters/#grace-period) tunnel run parameter. `cloudflared` connectors will now abide by the specified waiting period before forcefully closing connections to Cloudflare's network.
|
||||
- publish_date: "2024-08-06"
|
||||
title: cloudflared builds available in GitHub for Apple silicon
|
||||
description: |-
|
||||
macOS users can now download `cloudflared-arm64.pkg` directly from [GitHub](https://github.com/cloudflare/cloudflared/releases), in addition to being available via Homebrew.
|
||||
|
|
|
|||
|
|
@ -5,61 +5,61 @@ productLink: "/turnstile/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-08-12'
|
||||
description: |-
|
||||
- Added [`[flexible]`](/turnstile/get-started/client-side-rendering/#widget-size) width widget size.
|
||||
- Added new dimensions for Turnstile's compact size.
|
||||
- Added a Feedback Report toggle on the widget's configuration.
|
||||
- publish_date: '2024-04-10'
|
||||
description: |-
|
||||
- Added [`[refresh-timeout]`](/turnstile/get-started/client-side-rendering/#refresh-a-timed-out-widget) and document new automatic interactive timeout-refresh.
|
||||
- publish_date: '2024-03-25'
|
||||
description: |-
|
||||
- Added more [supported languages](/turnstile/reference/supported-languages).
|
||||
- publish_date: '2023-12-18'
|
||||
description: |-
|
||||
- Added [Pre-Clearance mode](/turnstile/concepts/pre-clearance-support/).
|
||||
- publish_date: '2023-08-24'
|
||||
description: |-
|
||||
- Added [Client-side errors](/turnstile/troubleshooting/client-side-errors/).
|
||||
- publish_date: '2023-07-31'
|
||||
description: |-
|
||||
- Added [`[turnstile.isExpired]`](/turnstile/get-started/client-side-rendering/#access-a-widgets-state).
|
||||
- Added `uk` language.
|
||||
- publish_date: '2023-05-25'
|
||||
description: |-
|
||||
- Added idempotency support for `POST /siteverify` requests via the `idempotency_key` parameter.
|
||||
- publish_date: '2023-04-17'
|
||||
description: |-
|
||||
- Added references to Turnstile Public API.
|
||||
- Added references for [`[after-interactive-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget), [`[before-interactive-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget), and [`[unsupported-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget).
|
||||
- publish_date: '2023-03-06'
|
||||
description: |-
|
||||
- Added [`[execution]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget) and [`[appearance]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget).
|
||||
- publish_date: '2023-02-15'
|
||||
description: |-
|
||||
- Added the [`[turnstile.ready]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget) callback.
|
||||
- publish_date: '2023-02-01'
|
||||
description: |-
|
||||
- Added the [`[data-]language`](/turnstile/get-started/client-side-rendering/#configurations) parameter.
|
||||
- publish_date: '2022-12-12'
|
||||
description: |-
|
||||
- [`POST /siteverify`](/turnstile/get-started/server-side-validation/) supports JSON requests now.
|
||||
- publish_date: '2022-11-11'
|
||||
description: |-
|
||||
- Added [`retry` and `retry-interval`](/turnstile/get-started/client-side-rendering/#configurations) for controlling retry behavior.
|
||||
- publish_date: '2022-10-28'
|
||||
description: |-
|
||||
- Renamed the `[data-]expired-callback` callback to [`[data-]timeout-callback`](/turnstile/get-started/client-side-rendering/#configurations) (called when the challenge times out).
|
||||
- Added the [`[data-]expired-callback`](/turnstile/get-started/client-side-rendering/#configurations) callback (called when the token expires).
|
||||
- publish_date: '2022-10-24'
|
||||
description: |-
|
||||
- Added [`response-field` and `response-field-name`](/turnstile/get-started/client-side-rendering/#configurations) for controlling the input element created by Turnstile.
|
||||
- Added option for changing the [size of the Turnstile widget](/turnstile/get-started/client-side-rendering/#widget-size).
|
||||
- publish_date: '2022-10-13'
|
||||
description: |-
|
||||
- Added validation for action: `/^[a-z0-9_-]{0,32}$/i`
|
||||
- Added validation for cData: `/^[a-z0-9_-]{0,255}$/i`
|
||||
- publish_date: '2022-10-11'
|
||||
description: |-
|
||||
- Added [`turnstile.remove`](/turnstile/get-started/client-side-rendering/#remove-a-widget)
|
||||
- publish_date: "2024-08-12"
|
||||
description: |-
|
||||
- Added [`[flexible]`](/turnstile/get-started/client-side-rendering/#widget-size) width widget size.
|
||||
- Added new dimensions for Turnstile's compact size.
|
||||
- Added a Feedback Report toggle on the widget's configuration.
|
||||
- publish_date: "2024-04-10"
|
||||
description: |-
|
||||
- Added [`[refresh-timeout]`](/turnstile/get-started/client-side-rendering/#refresh-a-timed-out-widget) and document new automatic interactive timeout-refresh.
|
||||
- publish_date: "2024-03-25"
|
||||
description: |-
|
||||
- Added more [supported languages](/turnstile/reference/supported-languages).
|
||||
- publish_date: "2023-12-18"
|
||||
description: |-
|
||||
- Added [Pre-Clearance mode](/turnstile/concepts/pre-clearance-support/).
|
||||
- publish_date: "2023-08-24"
|
||||
description: |-
|
||||
- Added [Client-side errors](/turnstile/troubleshooting/client-side-errors/).
|
||||
- publish_date: "2023-07-31"
|
||||
description: |-
|
||||
- Added [`[turnstile.isExpired]`](/turnstile/get-started/client-side-rendering/#access-a-widgets-state).
|
||||
- Added `uk` language.
|
||||
- publish_date: "2023-05-25"
|
||||
description: |-
|
||||
- Added idempotency support for `POST /siteverify` requests via the `idempotency_key` parameter.
|
||||
- publish_date: "2023-04-17"
|
||||
description: |-
|
||||
- Added references to Turnstile Public API.
|
||||
- Added references for [`[after-interactive-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget), [`[before-interactive-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget), and [`[unsupported-callback]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget).
|
||||
- publish_date: "2023-03-06"
|
||||
description: |-
|
||||
- Added [`[execution]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget) and [`[appearance]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget).
|
||||
- publish_date: "2023-02-15"
|
||||
description: |-
|
||||
- Added the [`[turnstile.ready]`](/turnstile/get-started/client-side-rendering/#explicitly-render-the-turnstile-widget) callback.
|
||||
- publish_date: "2023-02-01"
|
||||
description: |-
|
||||
- Added the [`[data-]language`](/turnstile/get-started/client-side-rendering/#configurations) parameter.
|
||||
- publish_date: "2022-12-12"
|
||||
description: |-
|
||||
- [`POST /siteverify`](/turnstile/get-started/server-side-validation/) supports JSON requests now.
|
||||
- publish_date: "2022-11-11"
|
||||
description: |-
|
||||
- Added [`retry` and `retry-interval`](/turnstile/get-started/client-side-rendering/#configurations) for controlling retry behavior.
|
||||
- publish_date: "2022-10-28"
|
||||
description: |-
|
||||
- Renamed the `[data-]expired-callback` callback to [`[data-]timeout-callback`](/turnstile/get-started/client-side-rendering/#configurations) (called when the challenge times out).
|
||||
- Added the [`[data-]expired-callback`](/turnstile/get-started/client-side-rendering/#configurations) callback (called when the token expires).
|
||||
- publish_date: "2022-10-24"
|
||||
description: |-
|
||||
- Added [`response-field` and `response-field-name`](/turnstile/get-started/client-side-rendering/#configurations) for controlling the input element created by Turnstile.
|
||||
- Added option for changing the [size of the Turnstile widget](/turnstile/get-started/client-side-rendering/#widget-size).
|
||||
- publish_date: "2022-10-13"
|
||||
description: |-
|
||||
- Added validation for action: `/^[a-z0-9_-]{0,32}$/i`
|
||||
- Added validation for cData: `/^[a-z0-9_-]{0,255}$/i`
|
||||
- publish_date: "2022-10-11"
|
||||
description: |-
|
||||
- Added [`turnstile.remove`](/turnstile/get-started/client-side-rendering/#remove-a-widget)
|
||||
|
|
|
|||
|
|
@ -5,12 +5,12 @@ productLink: "/version-management/"
|
|||
productArea: Core platform
|
||||
productAreaLink: /fundamentals/reference/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-02-26'
|
||||
title: "Support for API Shield"
|
||||
description: |-
|
||||
- [API Shield](/api-shield/) no longer prevents Version Management enablement and zone settings configurations.
|
||||
- publish_date: "2024-02-26"
|
||||
title: "Support for API Shield"
|
||||
description: |-
|
||||
- [API Shield](/api-shield/) no longer prevents Version Management enablement and zone settings configurations.
|
||||
|
||||
- publish_date: '2023-09-20'
|
||||
title: "Support for Bot Management"
|
||||
description: |-
|
||||
- Version Management now supports versioning for [Bot Management](/bots/plans/bm-subscription/).
|
||||
- publish_date: "2023-09-20"
|
||||
title: "Support for Bot Management"
|
||||
description: |-
|
||||
- Version Management now supports versioning for [Bot Management](/bots/plans/bm-subscription/).
|
||||
|
|
|
|||
|
|
@ -5,108 +5,108 @@ productLink: "/waf/"
|
|||
productArea: Application security
|
||||
productAreaLink: /fundamentals/reference/changelog/security/
|
||||
entries:
|
||||
- publish_date: '2024-09-16'
|
||||
scheduled_date: '2024-10-01'
|
||||
individual_page: true
|
||||
scheduled: true
|
||||
link: '/waf/change-log/scheduled-changes/'
|
||||
- publish_date: '2024-09-16'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-09-16/'
|
||||
- publish_date: '2024-09-03'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-09-03/'
|
||||
- publish_date: '2024-08-20'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-08-20---emergency-release/'
|
||||
- publish_date: '2024-08-19'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-08-19/'
|
||||
- publish_date: '2024-08-05'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-08-05/'
|
||||
- publish_date: '2024-07-29'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-07-29/'
|
||||
- publish_date: '2024-07-24'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-07-24/'
|
||||
- publish_date: '2024-07-17'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-07-17/'
|
||||
- publish_date: '2024-07-10'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-07-10/'
|
||||
- publish_date: '2024-06-18'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-06-18---emergency-release/'
|
||||
- publish_date: '2024-06-06'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-06-06---emergency-release/'
|
||||
- publish_date: '2024-05-30'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-30---emergency-release/'
|
||||
- publish_date: '2024-05-29'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-29---emergency-release/'
|
||||
- publish_date: '2024-05-21'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-21/'
|
||||
- publish_date: '2024-05-14'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-14/'
|
||||
- publish_date: '2024-05-08'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-08/'
|
||||
- publish_date: '2024-05-06'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-05-06/'
|
||||
- publish_date: '2024-04-24'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-04-24/'
|
||||
- publish_date: '2024-04-22'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-04-22/'
|
||||
- publish_date: '2024-04-16'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-04-16---emergency-release/'
|
||||
- publish_date: '2024-04-15'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-04-15/'
|
||||
- publish_date: '2024-04-08'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-04-08/'
|
||||
- publish_date: '2024-03-18'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-03-18/'
|
||||
- publish_date: '2024-03-11'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-03-11/'
|
||||
- publish_date: '2024-03-04'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-03-04/'
|
||||
- publish_date: '2024-02-26'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-02-26/'
|
||||
- publish_date: '2024-02-20'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-02-20/'
|
||||
- publish_date: '2024-02-12'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-02-12/'
|
||||
- publish_date: '2024-02-05'
|
||||
individual_page: true
|
||||
scheduled: true
|
||||
link: '/waf/change-log/2024-02-05/'
|
||||
- publish_date: '2024-01-22'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-01-22---emergency-release/'
|
||||
- publish_date: '2024-01-17'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-01-17---emergency-release/'
|
||||
- publish_date: '2024-01-16'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-01-16/'
|
||||
- publish_date: '2024-01-04'
|
||||
individual_page: true
|
||||
link: '/waf/change-log/2024-01-04/'
|
||||
- publish_date: "2024-09-16"
|
||||
scheduled_date: "2024-10-01"
|
||||
individual_page: true
|
||||
scheduled: true
|
||||
link: "/waf/change-log/scheduled-changes/"
|
||||
- publish_date: "2024-09-16"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-09-16/"
|
||||
- publish_date: "2024-09-03"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-09-03/"
|
||||
- publish_date: "2024-08-20"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-08-20---emergency-release/"
|
||||
- publish_date: "2024-08-19"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-08-19/"
|
||||
- publish_date: "2024-08-05"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-08-05/"
|
||||
- publish_date: "2024-07-29"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-07-29/"
|
||||
- publish_date: "2024-07-24"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-07-24/"
|
||||
- publish_date: "2024-07-17"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-07-17/"
|
||||
- publish_date: "2024-07-10"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-07-10/"
|
||||
- publish_date: "2024-06-18"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-06-18---emergency-release/"
|
||||
- publish_date: "2024-06-06"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-06-06---emergency-release/"
|
||||
- publish_date: "2024-05-30"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-30---emergency-release/"
|
||||
- publish_date: "2024-05-29"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-29---emergency-release/"
|
||||
- publish_date: "2024-05-21"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-21/"
|
||||
- publish_date: "2024-05-14"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-14/"
|
||||
- publish_date: "2024-05-08"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-08/"
|
||||
- publish_date: "2024-05-06"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-05-06/"
|
||||
- publish_date: "2024-04-24"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-04-24/"
|
||||
- publish_date: "2024-04-22"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-04-22/"
|
||||
- publish_date: "2024-04-16"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-04-16---emergency-release/"
|
||||
- publish_date: "2024-04-15"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-04-15/"
|
||||
- publish_date: "2024-04-08"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-04-08/"
|
||||
- publish_date: "2024-03-18"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-03-18/"
|
||||
- publish_date: "2024-03-11"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-03-11/"
|
||||
- publish_date: "2024-03-04"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-03-04/"
|
||||
- publish_date: "2024-02-26"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-02-26/"
|
||||
- publish_date: "2024-02-20"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-02-20/"
|
||||
- publish_date: "2024-02-12"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-02-12/"
|
||||
- publish_date: "2024-02-05"
|
||||
individual_page: true
|
||||
scheduled: true
|
||||
link: "/waf/change-log/2024-02-05/"
|
||||
- publish_date: "2024-01-22"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-01-22---emergency-release/"
|
||||
- publish_date: "2024-01-17"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-01-17---emergency-release/"
|
||||
- publish_date: "2024-01-16"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-01-16/"
|
||||
- publish_date: "2024-01-04"
|
||||
individual_page: true
|
||||
link: "/waf/change-log/2024-01-04/"
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ productLink: "/waiting-room/"
|
|||
productArea: Application performance
|
||||
productAreaLink: /fundamentals/reference/changelog/performance/
|
||||
entries:
|
||||
- publish_date: '2023-09-06'
|
||||
title: Waiting Room coverage for multiple hostnames and paths
|
||||
description: |-
|
||||
* Advanced Waiting Room customers can now [add multiple hostname and path combinations](/waiting-room/how-to/place-waiting-room/#apply-to-multiple-hostnames-and-paths) to a single waiting room via the UI and API.
|
||||
- publish_date: "2023-09-06"
|
||||
title: Waiting Room coverage for multiple hostnames and paths
|
||||
description: |-
|
||||
* Advanced Waiting Room customers can now [add multiple hostname and path combinations](/waiting-room/how-to/place-waiting-room/#apply-to-multiple-hostnames-and-paths) to a single waiting room via the UI and API.
|
||||
|
|
|
|||
|
|
@ -5,208 +5,207 @@ productLink: "/cloudflare-one/connections/connect-devices/warp/"
|
|||
productArea: Cloudflare One
|
||||
productAreaLink: /cloudflare-one/changelog/
|
||||
entries:
|
||||
- publish_date: "2024-08-26"
|
||||
title: WARP client for macOS (version 2024.8.309.1)
|
||||
description: |-
|
||||
A new beta release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos/distribution_groups/beta). This release contains minor fixes and improvements.
|
||||
|
||||
- publish_date: '2024-08-26'
|
||||
title: WARP client for macOS (version 2024.8.309.1)
|
||||
description: |-
|
||||
A new beta release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos/distribution_groups/beta). This release contains minor fixes and improvements.
|
||||
Notable updates:
|
||||
- Added the ability to customize PCAP options in `warp-cli`.
|
||||
- Added a list of installed applications in `warp-diag`.
|
||||
- Added a summary of `warp-dex` traceroute results in its JSON output.
|
||||
- Improved the performance of firewall operations when enforcing Split Tunnels configuration.
|
||||
- Fixed an issue where the DNS logs were not being cleared when the user switched configurations.
|
||||
- Fixed a known issue which required users to re-register when an older single configuration MDM file was deployed after deploying the newer, multiple configuration format.
|
||||
- Fixed an issue which prevented the use of private IP ranges that overlapped with end users' home networks.
|
||||
- Deprecated `warp-cli` commands have been removed. If you have any workflows that use the deprecated commands, update to the new commands where necessary.
|
||||
|
||||
Notable updates:
|
||||
- Added the ability to customize PCAP options in `warp-cli`.
|
||||
- Added a list of installed applications in `warp-diag`.
|
||||
- Added a summary of `warp-dex` traceroute results in its JSON output.
|
||||
- Improved the performance of firewall operations when enforcing Split Tunnels configuration.
|
||||
- Fixed an issue where the DNS logs were not being cleared when the user switched configurations.
|
||||
- Fixed a known issue which required users to re-register when an older single configuration MDM file was deployed after deploying the newer, multiple configuration format.
|
||||
- Fixed an issue which prevented the use of private IP ranges that overlapped with end users' home networks.
|
||||
- Deprecated `warp-cli` commands have been removed. If you have any workflows that use the deprecated commands, update to the new commands where necessary.
|
||||
Known issues:
|
||||
- Using MASQUE as the tunnel protocol may be incompatible if your organization has either of the following conditions:
|
||||
- Magic WAN is enabled but does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Regional Services is enabled.
|
||||
|
||||
Known issues:
|
||||
- Using MASQUE as the tunnel protocol may be incompatible if your organization has either of the following conditions:
|
||||
- Magic WAN is enabled but does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Regional Services is enabled.
|
||||
- publish_date: "2024-08-26"
|
||||
title: WARP client for Windows (version 2024.8.308.1)
|
||||
description: |-
|
||||
A new beta release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows/distribution_groups/beta). This release contains minor fixes and improvements.
|
||||
|
||||
- publish_date: '2024-08-26'
|
||||
title: WARP client for Windows (version 2024.8.308.1)
|
||||
description: |-
|
||||
A new beta release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows/distribution_groups/beta). This release contains minor fixes and improvements.
|
||||
Notable updates:
|
||||
- Added the ability to customize PCAP options in `warp-cli`.
|
||||
- Added a list of installed applications in `warp-diag`.
|
||||
- Added a summary of `warp-dex` traceroute results in its JSON output.
|
||||
- Improved the performance of firewall operations when enforcing Split Tunnels configuration.
|
||||
- Reduced the time it takes for a WARP client update to complete.
|
||||
- Fixed issues where incorrect DNS server addresses were being applied following reboots and network changes. Any incorrect static entries set by previous WARP versions must be manually reverted.
|
||||
- Fixed a known issue which required users to re-register when an older single configuration MDM file was deployed after deploying the newer, multiple configuration format.
|
||||
- Deprecated `warp-cli` commands have been removed. If you have any workflows that use the deprecated commands, update to the new commands where necessary.
|
||||
|
||||
Notable updates:
|
||||
- Added the ability to customize PCAP options in `warp-cli`.
|
||||
- Added a list of installed applications in `warp-diag`.
|
||||
- Added a summary of `warp-dex` traceroute results in its JSON output.
|
||||
- Improved the performance of firewall operations when enforcing Split Tunnels configuration.
|
||||
- Reduced the time it takes for a WARP client update to complete.
|
||||
- Fixed issues where incorrect DNS server addresses were being applied following reboots and network changes. Any incorrect static entries set by previous WARP versions must be manually reverted.
|
||||
- Fixed a known issue which required users to re-register when an older single configuration MDM file was deployed after deploying the newer, multiple configuration format.
|
||||
- Deprecated `warp-cli` commands have been removed. If you have any workflows that use the deprecated commands, update to the new commands where necessary.
|
||||
Known issues:
|
||||
- Using MASQUE as the tunnel protocol may be incompatible if your organization has either of the following conditions:
|
||||
- Magic WAN is enabled but does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Regional Services is enabled.
|
||||
- DNS resolution may be broken when all of the following conditions are true:
|
||||
- WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
|
||||
- A custom DNS server address is configured on the primary network adapter.
|
||||
- The custom DNS server address on the primary network adapter is changed while WARP is connected.
|
||||
|
||||
Known issues:
|
||||
- Using MASQUE as the tunnel protocol may be incompatible if your organization has either of the following conditions:
|
||||
- Magic WAN is enabled but does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Regional Services is enabled.
|
||||
- DNS resolution may be broken when all of the following conditions are true:
|
||||
- WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
|
||||
- A custom DNS server address is configured on the primary network adapter.
|
||||
- The custom DNS server address on the primary network adapter is changed while WARP is connected.
|
||||
To work around the DNS issue, reconnect the WARP client by toggling off and back on.
|
||||
|
||||
To work around the DNS issue, reconnect the WARP client by toggling off and back on.
|
||||
- publish_date: "2024-08-15"
|
||||
title: WARP client for Linux (version 2024.6.497.0)
|
||||
description: |-
|
||||
A new GA release for the Linux WARP client is now available in the [package repository](https://pkg.cloudflareclient.com/). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
|
||||
- publish_date: '2024-08-15'
|
||||
title: WARP client for Linux (version 2024.6.497.0)
|
||||
description: |-
|
||||
A new GA release for the Linux WARP client is now available in the [package repository](https://pkg.cloudflareclient.com/). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
New features:
|
||||
- The WARP client now supports operation on Ubuntu 24.04.
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
- TCP MSS clamping is now used where necessary to meet the MTU requirements of the tunnel interface. This will be especially helpful in Docker use cases.
|
||||
|
||||
New features:
|
||||
- The WARP client now supports operation on Ubuntu 24.04.
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
- TCP MSS clamping is now used where necessary to meet the MTU requirements of the tunnel interface. This will be especially helpful in Docker use cases.
|
||||
Warning:
|
||||
- Ubuntu 16.04 and 18.04 are not supported by this version of the client.
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
|
||||
Warning:
|
||||
- Ubuntu 16.04 and 18.04 are not supported by this version of the client.
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
Known issues:
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- The Linux client GUI does not yet support all GUI features found in the Windows and macOS clients. Future releases of the Linux client will be adding these GUI features.
|
||||
- The Zero Trust team name is not visible in the GUI if you upgraded from the previous GA release using an MDM tool.
|
||||
- Sometimes the WARP icon will remain gray (disconnected state) while in dark mode.
|
||||
|
||||
Known issues:
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. To check the migration status, contact your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- The Linux client GUI does not yet support all GUI features found in the Windows and macOS clients. Future releases of the Linux client will be adding these GUI features.
|
||||
- The Zero Trust team name is not visible in the GUI if you upgraded from the previous GA release using an MDM tool.
|
||||
- Sometimes the WARP icon will remain gray (disconnected state) while in dark mode.
|
||||
- publish_date: "2024-07-30"
|
||||
title: WARP client for macOS (version 2024.6.474.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This release contains fixes to improve the client; no new features are included.
|
||||
|
||||
- publish_date: '2024-07-30'
|
||||
title: WARP client for macOS (version 2024.6.474.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This release contains fixes to improve the client; no new features are included.
|
||||
Notable updates:
|
||||
- Fixed an issue which caused alternate network detection to fail if the beacon host was using TLS 1.2 without TLS Extended Master Secret (EMS) enabled.
|
||||
- Improved the stability of device profile switching based on alternate network detection.
|
||||
|
||||
Notable updates:
|
||||
- Fixed an issue which caused alternate network detection to fail if the beacon host was using TLS 1.2 without TLS Extended Master Secret (EMS) enabled.
|
||||
- Improved the stability of device profile switching based on alternate network detection.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- publish_date: "2024-07-30"
|
||||
title: WARP client for Windows (version 2024.6.473.0)
|
||||
description: |-
|
||||
A new GA release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows-1/distribution_groups/release). This release contains fixes to improve the client; no new features are included.
|
||||
|
||||
- publish_date: '2024-07-30'
|
||||
title: WARP client for Windows (version 2024.6.473.0)
|
||||
description: |-
|
||||
A new GA release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows-1/distribution_groups/release). This release contains fixes to improve the client; no new features are included.
|
||||
Notable updates:
|
||||
- Fixed an issue which caused alternate network detection to fail if the beacon host was using TLS 1.2 without TLS Extended Master Secret (EMS) enabled.
|
||||
- Improved the stability of device profile switching based on alternate network detection.
|
||||
|
||||
Notable updates:
|
||||
- Fixed an issue which caused alternate network detection to fail if the beacon host was using TLS 1.2 without TLS Extended Master Secret (EMS) enabled.
|
||||
- Improved the stability of device profile switching based on alternate network detection.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- publish_date: "2024-06-28"
|
||||
title: WARP client for macOS (version 2024.6.416.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
|
||||
- publish_date: '2024-06-28'
|
||||
title: WARP client for macOS (version 2024.6.416.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
New features:
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
|
||||
New features:
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
Additional changes and improvements:
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `/Library/Application Support/Cloudflare/installed_cert.pem`.
|
||||
- Fixed an issue where re-auth notifications were not cleared from the UI when the user switched configurations.
|
||||
- Fixed a macOS firewall rule that allowed all UDP traffic to go outside the tunnel. Relates to TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)).
|
||||
- Fixed an issue that could cause the Cloudflare WARP menu bar application to disappear when switching configurations.
|
||||
|
||||
Additional changes and improvements:
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `/Library/Application Support/Cloudflare/installed_cert.pem`.
|
||||
- Fixed an issue where re-auth notifications were not cleared from the UI when the user switched configurations.
|
||||
- Fixed a macOS firewall rule that allowed all UDP traffic to go outside the tunnel. Relates to TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)).
|
||||
- Fixed an issue that could cause the Cloudflare WARP menu bar application to disappear when switching configurations.
|
||||
Warning:
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
|
||||
Warning:
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- publish_date: "2024-06-28"
|
||||
title: WARP client for Windows (version 2024.6.415.0)
|
||||
description: |-
|
||||
A new GA release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows-1/distribution_groups/release). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
|
||||
- publish_date: '2024-06-28'
|
||||
title: WARP client for Windows (version 2024.6.415.0)
|
||||
description: |-
|
||||
A new GA release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows-1/distribution_groups/release). This release includes some exciting new features. It also includes additional fixes and minor improvements.
|
||||
New features:
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The ZT WARP client on Windows devices can now connect before the user completes their Windows login. This [Windows pre-login capability](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/windows-prelogin/) allows for connecting to on-premise Active Directory and/or similar resources necessary to complete the Windows login.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
|
||||
New features:
|
||||
- Admins can now elect to have ZT WARP clients connect using the MASQUE protocol; this setting is in Device Profiles. Note: before MASQUE can be used, the global setting for Override local interface IP must be enabled. For more detail, refer to [Device tunnel protocol](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#device-tunnel-protocol). This feature will be rolled out to customers in stages over approximately the next month.
|
||||
- The ZT WARP client on Windows devices can now connect before the user completes their Windows login. This [Windows pre-login capability](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/windows-prelogin/) allows for connecting to on-premise Active Directory and/or similar resources necessary to complete the Windows login.
|
||||
- The Device Posture [client certificate check](/cloudflare-one/identity/devices/warp-client-checks/client-certificate/) has been substantially enhanced. The primary enhancement is the ability to check for client certificates that have unique common names, made unique by the inclusion of the device serial number or host name (for example, CN = `123456.mycompany`, where 123456 is the device serial number).
|
||||
Additional changes and improvements:
|
||||
- Added a new [Unable to Connect message](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_failed_read_system_dns_config) to the UI to help in troubleshooting.
|
||||
- The upgrade window now uses international date formats.
|
||||
- Made a change to ensure DEX tests are not running when the tunnel is not up due to the device going to or waking from sleep. This is specific to devices using the S3 power model.
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `%ProgramData%\Cloudflare\installed_cert.pem`.
|
||||
- Fixed an issue where ICMPv6 Neighbor Solicitation messages were being incorrectly sent on the WARP tunnel.
|
||||
- Fixed an issue where a silent upgrade was causing certain files to be deleted if the target upgrade version is the same as the current version.
|
||||
|
||||
Additional changes and improvements:
|
||||
- Added a new [Unable to Connect message](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_failed_read_system_dns_config) to the UI to help in troubleshooting.
|
||||
- The upgrade window now uses international date formats.
|
||||
- Made a change to ensure DEX tests are not running when the tunnel is not up due to the device going to or waking from sleep. This is specific to devices using the S3 power model.
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `%ProgramData%\Cloudflare\installed_cert.pem`.
|
||||
- Fixed an issue where ICMPv6 Neighbor Solicitation messages were being incorrectly sent on the WARP tunnel.
|
||||
- Fixed an issue where a silent upgrade was causing certain files to be deleted if the target upgrade version is the same as the current version.
|
||||
Warning:
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
|
||||
Warning:
|
||||
- This is the last GA release that will be supporting older, deprecated `warp-cli` commands. There are two methods to identify these commands. One, when used in this release, the command will work but will also return a deprecation warning. And two, the deprecated commands do not appear in the output of `warp-cli -h`.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the [switch configurations](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/switch-organizations/) feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
- There are certain known limitations preventing the use of the MASQUE tunnel protocol in certain scenarios. Do not use the MASQUE tunnel protocol if:
|
||||
- A Magic WAN integration is on the account and does not have the latest packet flow path for WARP traffic. Please check migration status with your account team.
|
||||
- Your account has Regional Services enabled.
|
||||
- publish_date: "2024-06-27"
|
||||
title: Cloudflare One Agent for iOS (version 1.4)
|
||||
description: |-
|
||||
A new GA release for the iOS Cloudflare One Agent is now available in the [iOS App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492).
|
||||
|
||||
- publish_date: '2024-06-27'
|
||||
title: Cloudflare One Agent for iOS (version 1.4)
|
||||
description: |-
|
||||
A new GA release for the iOS Cloudflare One Agent is now available in the [iOS App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492).
|
||||
Notable updates:
|
||||
- Fixed an issue with endpoint IP settings in MDM files
|
||||
- Cleaned up some erroneous links
|
||||
- Updated the Terms of Service
|
||||
|
||||
Notable updates:
|
||||
- Fixed an issue with endpoint IP settings in MDM files
|
||||
- Cleaned up some erroneous links
|
||||
- Updated the Terms of Service
|
||||
- publish_date: "2024-05-22"
|
||||
title: WARP client for Windows (version 2024.5.310.1)
|
||||
description: |-
|
||||
A new beta release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows/distribution_groups/beta).
|
||||
|
||||
- publish_date: '2024-05-22'
|
||||
title: WARP client for Windows (version 2024.5.310.1)
|
||||
description: |-
|
||||
A new beta release for the Windows WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-windows/distribution_groups/beta).
|
||||
|
||||
Notable updates:
|
||||
- Added a new [Unable to Connect message](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_failed_read_system_dns_config) to the UI to help in troubleshooting.
|
||||
- In the upgrade window, a change was made to use international date formats to resolve an issue with localization.
|
||||
- Made a change to ensure DEX tests are not running when the tunnel is not up due to the device going to or waking from sleep. This is specific to devices using the S3 power model.
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `%ProgramData%\Cloudflare\installed_cert.pem`.
|
||||
- Fixed an issue where ICMPv6 Neighbor Solicitation messages were being incorrectly sent on the WARP tunnel.
|
||||
Notable updates:
|
||||
- Added a new [Unable to Connect message](/cloudflare-one/connections/connect-devices/warp/troubleshooting/client-errors/#cf_failed_read_system_dns_config) to the UI to help in troubleshooting.
|
||||
- In the upgrade window, a change was made to use international date formats to resolve an issue with localization.
|
||||
- Made a change to ensure DEX tests are not running when the tunnel is not up due to the device going to or waking from sleep. This is specific to devices using the S3 power model.
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `%ProgramData%\Cloudflare\installed_cert.pem`.
|
||||
- Fixed an issue where ICMPv6 Neighbor Solicitation messages were being incorrectly sent on the WARP tunnel.
|
||||
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the switch configurations feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the switch configurations feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
|
||||
- publish_date: '2024-05-21'
|
||||
title: WARP client for macOS (version 2024.5.287.1)
|
||||
description: |-
|
||||
A new beta release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos/distribution_groups/beta)
|
||||
- publish_date: "2024-05-21"
|
||||
title: WARP client for macOS (version 2024.5.287.1)
|
||||
description: |-
|
||||
A new beta release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos/distribution_groups/beta)
|
||||
|
||||
Notable updates:
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `/Library/Application Support/Cloudflare/installed_cert.pem`.
|
||||
- Fixed an issue so that the reauth notification is cleared from the UI when the user switches configurations.
|
||||
- Fixed an issue by correcting the WARP client setting of macOS firewall rules. This relates to TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)).
|
||||
- Fixed an issue that could cause the Cloudflare WARP menu bar application to disappear when switching configurations.
|
||||
Notable updates:
|
||||
- Fixed a known issue where the certificate was not always properly left behind in `/Library/Application Support/Cloudflare/installed_cert.pem`.
|
||||
- Fixed an issue so that the reauth notification is cleared from the UI when the user switches configurations.
|
||||
- Fixed an issue by correcting the WARP client setting of macOS firewall rules. This relates to TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)).
|
||||
- Fixed an issue that could cause the Cloudflare WARP menu bar application to disappear when switching configurations.
|
||||
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the switch configurations feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
Known issues:
|
||||
- If a user has an MDM file configured to support multiple profiles (for the switch configurations feature), and then changes to an MDM file configured for a single profile, the WARP client may not connect. The workaround is to use the `warp-cli registration delete` command to clear the registration, and then re-register the client.
|
||||
|
||||
- publish_date: '2024-05-10'
|
||||
title: Cloudflare One Agent for Android (version 1.7)
|
||||
description: |-
|
||||
A new GA release for the Android Cloudflare One Agent is now available in the [Google Play Store](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent). This release fixes an issue where the user was not prompted to select the client certificate in the browser during Access registration.
|
||||
- publish_date: "2024-05-10"
|
||||
title: Cloudflare One Agent for Android (version 1.7)
|
||||
description: |-
|
||||
A new GA release for the Android Cloudflare One Agent is now available in the [Google Play Store](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent). This release fixes an issue where the user was not prompted to select the client certificate in the browser during Access registration.
|
||||
|
||||
- publish_date: '2024-05-09'
|
||||
title: Crowdstrike posture checks for online status
|
||||
description: |-
|
||||
Two new Crowdstrike attributes, _Last Seen_ and _State_, are now available to be used as selectors in the [Crowdstrike service provider integration](/cloudflare-one/identity/devices/service-providers/crowdstrike/).
|
||||
- publish_date: "2024-05-09"
|
||||
title: Crowdstrike posture checks for online status
|
||||
description: |-
|
||||
Two new Crowdstrike attributes, _Last Seen_ and _State_, are now available to be used as selectors in the [Crowdstrike service provider integration](/cloudflare-one/identity/devices/service-providers/crowdstrike/).
|
||||
|
||||
- publish_date: '2024-05-08'
|
||||
title: WARP client for macOS (version 2024.3.444.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This releases fixes an issue with how the WARP client sets macOS firewall rules and addresses the TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)) vulnerability.
|
||||
- publish_date: "2024-05-08"
|
||||
title: WARP client for macOS (version 2024.3.444.0)
|
||||
description: |-
|
||||
A new GA release for the macOS WARP client is now available in the [App Center](https://install.appcenter.ms/orgs/cloudflare/apps/1.1.1.1-macos-1/distribution_groups/release). This releases fixes an issue with how the WARP client sets macOS firewall rules and addresses the TunnelVision ([CVE-2024-3661](https://nvd.nist.gov/vuln/detail/CVE-2024-3661)) vulnerability.
|
||||
|
|
|
|||
|
|
@ -5,61 +5,59 @@ productLink: "/workers-ai/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: "2024-07-23"
|
||||
title: Meta Llama 3.1 now available on Workers AI
|
||||
description: |-
|
||||
Workers AI now suppoorts [Meta Llama 3.1](/workers-ai/models/llama-3.1-8b-instruct/).
|
||||
|
||||
- publish_date: '2024-07-23'
|
||||
title: Meta Llama 3.1 now available on Workers AI
|
||||
description: |-
|
||||
Workers AI now suppoorts [Meta Llama 3.1](/workers-ai/models/llama-3.1-8b-instruct/).
|
||||
- publish_date: "2024-07-11"
|
||||
title: New community-contributed tutorial
|
||||
description: |-
|
||||
- Added community contributed tutorial on how to [create APIs to recommend products on e-commerce sites using Workers AI and Stripe](/developer-spotlight/tutorials/creating-a-recommendation-api/).
|
||||
|
||||
- publish_date: '2024-07-11'
|
||||
title: New community-contributed tutorial
|
||||
description: |-
|
||||
- Added community contributed tutorial on how to [create APIs to recommend products on e-commerce sites using Workers AI and Stripe](/developer-spotlight/tutorials/creating-a-recommendation-api/).
|
||||
- publish_date: "2024-06-27"
|
||||
title: Introducing embedded function calling
|
||||
description: |-
|
||||
- A new way to do function calling with [Embedded function calling](/workers-ai/function-calling/embedded)
|
||||
- Published new [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) npm package
|
||||
- Open-sourced [`ai-utils on Github`](https://github.com/cloudflare/ai-utils)
|
||||
|
||||
- publish_date: '2024-06-27'
|
||||
title: Introducing embedded function calling
|
||||
description: |-
|
||||
- A new way to do function calling with [Embedded function calling](/workers-ai/function-calling/embedded)
|
||||
- Published new [`@cloudflare/ai-utils`](https://www.npmjs.com/package/@cloudflare/ai-utils) npm package
|
||||
- Open-sourced [`ai-utils on Github`](https://github.com/cloudflare/ai-utils)
|
||||
- publish_date: "2024-06-19"
|
||||
title: Added support for traditional function calling
|
||||
description: |-
|
||||
- [Function calling](/workers-ai/function-calling/) is now supported on enabled models
|
||||
- Properties added on [models](/workers-ai/models/) page to show which models support function calling
|
||||
|
||||
- publish_date: '2024-06-19'
|
||||
title: Added support for traditional function calling
|
||||
description: |-
|
||||
- [Function calling](/workers-ai/function-calling/) is now supported on enabled models
|
||||
- Properties added on [models](/workers-ai/models/) page to show which models support function calling
|
||||
- publish_date: "2024-06-18"
|
||||
title: Native support for AI Gateways
|
||||
description: |-
|
||||
Workers AI now natively supports [AI Gateway](/ai-gateway/providers/workersai/#worker).
|
||||
|
||||
- publish_date: '2024-06-18'
|
||||
title: Native support for AI Gateways
|
||||
description: |-
|
||||
Workers AI now natively supports [AI Gateway](/ai-gateway/providers/workersai/#worker).
|
||||
- publish_date: "2024-06-11"
|
||||
title: Deprecation announcement for `@cf/meta/llama-2-7b-chat-int8`
|
||||
description: |-
|
||||
We will be deprecating `@cf/meta/llama-2-7b-chat-int8` on 2024-06-30.
|
||||
|
||||
- publish_date: '2024-06-11'
|
||||
title: Deprecation announcement for `@cf/meta/llama-2-7b-chat-int8`
|
||||
description: |-
|
||||
We will be deprecating `@cf/meta/llama-2-7b-chat-int8` on 2024-06-30.
|
||||
Replace the model ID in your code with a new model of your choice:
|
||||
- [`@cf/meta/llama-3-8b-instruct`](/workers-ai/models/llama-3-8b-instruct/) is the newest model in the Llama family (and is currently free for a limited time on Workers AI).
|
||||
- [`@cf/meta/llama-3-8b-instruct-awq`](/workers-ai/models/llama-3-8b-instruct-awq/) is the new Llama 3 in a similar precision to your currently selected model. This model is also currently free for a limited time.
|
||||
|
||||
Replace the model ID in your code with a new model of your choice:
|
||||
- [`@cf/meta/llama-3-8b-instruct`](/workers-ai/models/llama-3-8b-instruct/) is the newest model in the Llama family (and is currently free for a limited time on Workers AI).
|
||||
- [`@cf/meta/llama-3-8b-instruct-awq`](/workers-ai/models/llama-3-8b-instruct-awq/) is the new Llama 3 in a similar precision to your currently selected model. This model is also currently free for a limited time.
|
||||
If you do not switch to a different model by June 30th, we will automatically start returning inference from `@cf/meta/llama-3-8b-instruct-awq`.
|
||||
|
||||
If you do not switch to a different model by June 30th, we will automatically start returning inference from `@cf/meta/llama-3-8b-instruct-awq`.
|
||||
- publish_date: "2024-05-29"
|
||||
title: Add new public LoRAs and note on LoRA routing
|
||||
description: |-
|
||||
* Added documentation on [new public LoRAs](/workers-ai/fine-tunes/public-loras/).
|
||||
* Noted that you can now run LoRA inference with the base model rather than explicitly calling the `-lora` version
|
||||
|
||||
- publish_date: '2024-05-29'
|
||||
title: Add new public LoRAs and note on LoRA routing
|
||||
description: |-
|
||||
* Added documentation on [new public LoRAs](/workers-ai/fine-tunes/public-loras/).
|
||||
* Noted that you can now run LoRA inference with the base model rather than explicitly calling the `-lora` version
|
||||
- publish_date: "2024-05-17"
|
||||
title: Add OpenAI compatible API endpoints
|
||||
description: |-
|
||||
Added OpenAI compatible API endpoints for `/v1/chat/completions` and `/v1/embeddings`. For more details, refer to [Configurations](/workers-ai/configuration/open-ai-compatibility/).
|
||||
|
||||
|
||||
- publish_date: '2024-05-17'
|
||||
title: Add OpenAI compatible API endpoints
|
||||
description: |-
|
||||
Added OpenAI compatible API endpoints for `/v1/chat/completions` and `/v1/embeddings`. For more details, refer to [Configurations](/workers-ai/configuration/open-ai-compatibility/).
|
||||
|
||||
- publish_date: '2024-04-11'
|
||||
title: Add AI native binding
|
||||
description: |-
|
||||
* Added new AI native binding, you can now run models with `const resp = await env.AI.run(modelName, inputs)`
|
||||
* Deprecated `@cloudflare/ai` npm package. While existing solutions using the @cloudflare/ai package will continue to work, no new Workers AI features will be supported.
|
||||
Moving to native AI bindings is highly recommended
|
||||
- publish_date: "2024-04-11"
|
||||
title: Add AI native binding
|
||||
description: |-
|
||||
* Added new AI native binding, you can now run models with `const resp = await env.AI.run(modelName, inputs)`
|
||||
* Deprecated `@cloudflare/ai` npm package. While existing solutions using the @cloudflare/ai package will continue to work, no new Workers AI features will be supported.
|
||||
Moving to native AI bindings is highly recommended
|
||||
|
|
|
|||
|
|
@ -5,231 +5,231 @@ productLink: "/workers/"
|
|||
productArea: Developer platform
|
||||
productAreaLink: /workers/platform/changelog/platform/
|
||||
entries:
|
||||
- publish_date: '2024-08-19'
|
||||
description: |-
|
||||
- Workers now support the [`allow_custom_ports` compatibility flag](/workers/configuration/compatibility-dates/#allow-specifying-a-custom-port-when-making-a-subrequest-with-the-fetch-api) which enables using the `fetch()` calls to custom ports.
|
||||
- publish_date: '2024-08-15'
|
||||
description: |-
|
||||
- Updated v8 to version 12.8.
|
||||
- You can now use [`Promise.try()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/try) in Cloudflare Workers. Refer to [`tc39/proposal-promise-try`](https://github.com/tc39/proposal-promise-try) for more context on this API that has recently been added to the JavaScript language.
|
||||
- publish_date: '2024-08-14'
|
||||
description: |-
|
||||
- When using the `nodejs_compat_v2` compatibility flag, the `setImmediate(fn)` API from Node.js is now available at the global scope.
|
||||
- The `internal_writable_stream_abort_clears_queue` compatibility flag will ensure that certain `WritableStream` `abort()` operations are handled immediately rather than lazily, ensuring that the stream is appropriately aborted when the consumer of the stream is no longer active.
|
||||
- publish_date: '2024-07-19'
|
||||
description: |-
|
||||
- Workers with the [mTLS](/workers/runtime-apis/bindings/mtls/) binding now support [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/).
|
||||
- publish_date: '2024-07-18'
|
||||
description: |-
|
||||
- Added a new `truncated` flag to [Tail Worker](/workers/observability/logging/tail-workers/) events to indicate when the event buffer is full and events are being dropped.
|
||||
- publish_date: '2024-07-17'
|
||||
description: |-
|
||||
- Updated v8 to version 12.7.
|
||||
- publish_date: '2024-07-11'
|
||||
description: |-
|
||||
- Added community contributed tutorial on how to create [custom access control for files in R2 using D1 and Workers](/developer-spotlight/tutorials/custom-access-control-for-files/).
|
||||
- Added community contributed tutorial on how to [send form submissions using Astro and Resend](/developer-spotlight/tutorials/handle-form-submission-with-astro-resend/).
|
||||
- Added community contributed tutorial on how to [create a sitemap from Sanity CMS with Workers](/developer-spotlight/tutorials/create-sitemap-from-sanity-cms/).
|
||||
- publish_date: '2024-07-03'
|
||||
description: |-
|
||||
- The [`node:crypto`](/workers/runtime-apis/nodejs/crypto/) implementation now includes the scrypt(...) and scryptSync(...) APIs.
|
||||
- Workers now support the standard [EventSource](/workers/runtime-apis/eventsource/) API.
|
||||
- Fixed a bug where when writing to an HTTP Response body would sometimes hang when the client disconnected (and sometimes throw an exception). It will now always throw an exception.
|
||||
- publish_date: '2024-07-01'
|
||||
description: |-
|
||||
- When using [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/), you can now use [version overrides](/workers/configuration/versions-and-deployments/gradual-deployments/#version-overrides) to send a request to a specific version of your Worker.
|
||||
- publish_date: '2024-06-28'
|
||||
description: |-
|
||||
- Fixed a bug which caused `Date.now()` to return skewed results if called before the first I/O of the first request after a Worker first started up. The value returned would be offset backwards by the amount of CPU time spent starting the Worker (compiling and running global scope), making it seem like the first I/O (e.g. first fetch()) was slower than it really was. This skew had nothing to do with Spectre mitigations; it was simply a longstanding bug.
|
||||
- publish_date: '2024-06-24'
|
||||
description: |-
|
||||
- [Exceptions](/durable-objects/best-practices/error-handling) thrown from Durable Object internal operations and tunneled to the caller may now be populated with a `.retryable: true` property if the exception was likely due to a transient failure, or populated with an `.overloaded: true` property if the exception was due to [overload](/durable-objects/observability/troubleshooting/#durable-object-is-overloaded).
|
||||
- publish_date: '2024-06-20'
|
||||
description: |-
|
||||
- We now prompt for extra confirmation if attempting to rollback to a version of a Worker using the [Deployments API](/api/operations/worker-deployments-create-deployment) where the value of a secret is different than the currently deployed version. A `?force=true` query parameter can be specified to proceed with the rollback.
|
||||
- publish_date: '2024-06-19'
|
||||
description: |-
|
||||
- When using [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/), the `buffer` module now has an implementation of `isAscii()` and `isUtf8()` methods.
|
||||
- Fixed a bug where exceptions propagated from [JS RPC](/workers/runtime-apis/rpc) calls to Durable Objects would lack the `.remote` property that exceptions from `fetch()` calls to Durable Objects have.
|
||||
- publish_date: '2024-06-12'
|
||||
description: |-
|
||||
- Blob and Body objects now include a new `bytes()` method, reflecting [recent](https://w3c.github.io/FileAPI/#bytes-method-algo) [additions](https://fetch.spec.whatwg.org/#dom-body-bytes) to web standards.
|
||||
- publish_date: '2024-06-03'
|
||||
description: |-
|
||||
- Workers with [Smart Placement](/workers/configuration/smart-placement/) enabled now support [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/).
|
||||
- publish_date: '2024-05-17'
|
||||
description: |-
|
||||
- Updated v8 to version 12.6.
|
||||
- publish_date: '2024-05-15'
|
||||
description: |-
|
||||
- The new [`fetch_standard_url` compatibility flag](/workers/configuration/compatibility-dates/#use-standard-url-parsing-in-fetch) will become active by default on June 3rd, 2024 and ensures that URLs passed into the `fetch(...)` API, the `new Request(...)` constructor, and redirected requests will be parsed using the standard WHATWG URL parser.
|
||||
- DigestStream is now more efficient and exposes a new `bytesWritten` property that indicates that number of bytes written to the digest.
|
||||
- publish_date: '2024-05-13'
|
||||
description: |-
|
||||
- Updated v8 to version 12.5.
|
||||
- A bug in the fetch API implementation would cause the content type of a Blob to be incorrectly set. The fix is being released behind a new [`blob_standard_mime_type` compatibility flag](/workers/configuration/compatibility-dates/#properly-extract-blob-mime-type-from-content-type-headers).
|
||||
- publish_date: '2024-05-03'
|
||||
description: |-
|
||||
- Fixed RPC to/from Durable Objects not honoring the output gate.
|
||||
- The `internal_stream_byob_return_view` compatibility flag can be used to improve the standards compliance of the `ReadableStreamBYOBReader` implementation when working with BYOB streams provided by the runtime (like in `response.body` or `request.body`). The flag ensures that the final read result will always include a `value` field whose value is set to an empty `Uint8Array` whose underlying `ArrayBuffer` is the same memory allocation as the one passed in on the call to `read()`.
|
||||
- The Web platform standard `reportError(err)` global API is now available in workers. The reported error will first be emitted as an 'error' event on the global scope then reported in both the console output and tail worker exceptions by default.
|
||||
- publish_date: '2024-04-26'
|
||||
description: |-
|
||||
- Updated v8 to version 12.4.
|
||||
- publish_date: '2024-04-11'
|
||||
description: |-
|
||||
- Improve Streams API spec compliance by exposing `desiredSize` and other properties on stream class prototypes
|
||||
- The new `URL.parse(...)` method is implemented. This provides an alternative to the URL constructor that does not throw exceptions on invalid URLs.
|
||||
- R2 bindings objects now have a `storageClass` option. This can be set on object upload to specify the R2 storage class - Standard or Infrequent Access. The property is also returned with object metadata.
|
||||
- publish_date: '2024-04-05'
|
||||
description: |-
|
||||
- A new [JavaScript-native remote procedure call (RPC) API](/workers/runtime-apis/rpc) is now available, allowing you to communicate more easily across Workers and between Workers and Durable Objects.
|
||||
- publish_date: '2024-04-04'
|
||||
description: |-
|
||||
- There is no longer an explicit limit on the total amount of data which may be uploaded with Cache API [`put()`](/workers/runtime-apis/cache/#put) per request. Other [Cache API Limits](/workers/platform/limits/#cache-api-limits) continue to apply.
|
||||
- The Web standard `ReadableStream.from()` API is now implemented. The API enables creating a `ReadableStream` from a either a sync or async iterable.
|
||||
- publish_date: '2024-04-03'
|
||||
description: |-
|
||||
- When the [`brotli_content_encoding`](/workers/configuration/compatibility-dates/#brotli-content-encoding-support) compatibility flag is enabled, the Workers runtime now supports compressing and decompressing request bodies encoded using the [Brotli](https://developer.mozilla.org/en-US/docs/Glossary/Brotli_compression) compression algorithm. Refer to [this docs section](/workers/runtime-apis/fetch/#how-the-accept-encoding-header-is-handled) for more detail.
|
||||
- publish_date: '2024-04-02'
|
||||
description: |-
|
||||
- You can now [write Workers in Python](/workers/languages/python)
|
||||
- publish_date: '2024-04-01'
|
||||
description: |-
|
||||
- The new [`unwrap_custom_thenables` compatibility flag](/workers/configuration/compatibility-dates/#handling-custom-thenables) enables workers to accept custom thenables in internal APIs that expect a promise (for instance, the `ctx.waitUntil(...)` method).
|
||||
- TransformStreams created with the TransformStream constructor now have a cancel algorithm that is called when the stream is canceled or aborted. This change is part of the implementation of the WHATWG Streams standard.
|
||||
- The [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/) now includes an implementation of the [`MockTracker` API from `node:test`](https://nodejs.org/api/test.html#class-mocktracker). This is not an implementation of the full `node:test` module, and mock timers are currently not included.
|
||||
- Exceptions reported to [Tail Workers](/workers/observability/logging/tail-workers/) now include a "stack" property containing the exception's stack trace, if available.
|
||||
- publish_date: '2024-03-11'
|
||||
description: |-
|
||||
- Built-in APIs that return Promises will now produce stack traces when the Promise rejects. Previously, the rejection error lacked a stack trace.
|
||||
- A new compat flag `fetcher_no_get_put_delete` removes the `get()`, `put()`, and `delete()` methods on service bindings and Durable Object stubs. This will become the default as of compatibility date 2024-03-26. These methods were designed as simple convenience wrappers around `fetch()`, but were never documented.
|
||||
- Updated v8 to version 12.3.
|
||||
- publish_date: '2024-02-24'
|
||||
description: |-
|
||||
- v8 updated to version 12.2.
|
||||
- You can now use [Iterator helpers](https://v8.dev/features/iterator-helpers) in Workers.
|
||||
- You can now use [new methods on `Set`](https://github.com/tc39/proposal-set-methods), such as `Set.intersection` and `Set.union`, in Workers.
|
||||
- publish_date: '2024-02-23'
|
||||
description: |-
|
||||
- Sockets now support an [`opened`](/workers/runtime-apis/tcp-sockets/#socket) attribute.
|
||||
- [Durable Object alarm handlers](/durable-objects/api/alarms/#alarm) now impose a maximum wall time of 15 minutes.
|
||||
- publish_date: '2023-12-04'
|
||||
description: |-
|
||||
- The Web Platform standard [`navigator.sendBeacon(...)` API](/workers/runtime-apis/web-standards#navigatorsendbeaconurl-data) is now provided by the Workers runtime.
|
||||
- V8 updated to 12.0.
|
||||
- publish_date: '2023-10-30'
|
||||
description: |-
|
||||
- A new usage model called [Workers Standard](/workers/platform/pricing/#workers) is available for Workers and Pages Functions pricing. This is now the default usage model for accounts that are first upgraded to the Workers Paid plan. Read the [blog post](https://blog.cloudflare.com/workers-pricing-scale-to-zero/) for more information.
|
||||
- The usage model set in a script's wrangler.toml will be ignored after an account has opted-in to [Workers Standard](/workers/platform/pricing/#workers) pricing. It must be configured through the dashboard (Workers & Pages > Select your Worker > Settings > Usage Model).
|
||||
- Workers and Pages Functions on the Standard usage model can set custom [CPU limits](/workers/wrangler/configuration/#limits) for their Workers
|
||||
- publish_date: '2023-10-20'
|
||||
description: |-
|
||||
- Added the [`crypto_preserve_public_exponent`](/workers/configuration/compatibility-dates/#webcrypto-preserve-publicexponent-field)
|
||||
compatibility flag to correct a wrong type being used in the algorithm field of RSA keys in
|
||||
the WebCrypto API.
|
||||
- publish_date: '2023-10-18'
|
||||
description: |-
|
||||
- The limit of 3 Cron Triggers per Worker has been removed. Account-level limits on the total number of
|
||||
Cron Triggers across all Workers still apply.
|
||||
- publish_date: '2023-10-12'
|
||||
description: |-
|
||||
- A [TCP Socket](/workers/runtime-apis/tcp-sockets/)'s WritableStream now ensures the connection has opened before resolving the promise returned by `close`.
|
||||
- publish_date: '2023-10-09'
|
||||
description: |-
|
||||
- The Web Platform standard [`CustomEvent` class](https://dom.spec.whatwg.org/#interface-customevent) is now available in Workers.
|
||||
- Fixed a bug in the WebCrypto API where the `publicExponent` field of the algorithm of RSA keys would have the wrong type. Use the [`crypto_preserve_public_exponent` compatibility flag](/workers/configuration/compatibility-dates/#webcrypto-preserve-publicexponent-field) to enable the new behavior.
|
||||
- publish_date: '2023-09-14'
|
||||
description: |-
|
||||
- An implementation of the [`node:crypto`](/workers/runtime-apis/nodejs/crypto/)
|
||||
API from Node.js is now available when the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/)
|
||||
is enabled.
|
||||
- publish_date: '2023-07-14'
|
||||
description: |-
|
||||
- An implementation of the [`util.MIMEType`](https://nodejs.org/api/util.html#class-utilmimetype)
|
||||
API from Node.js is now available when the [`nodejs_compat` compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/)
|
||||
is enabled.
|
||||
- publish_date: '2023-07-07'
|
||||
description: |-
|
||||
- An implementation of the [`process.env`](/workers/runtime-apis/nodejs/process) API from Node.js is now available when using the `nodejs_compat` compatibility flag.
|
||||
- An implementation of the [`diagnostics_channel`](/workers/runtime-apis/nodejs/diagnostics-channel) API from Node.js is now available when using the `nodejs_compat` compatibility flag.
|
||||
- publish_date: '2023-06-22'
|
||||
description: |-
|
||||
- Added the [`strict_crypto_checks`](/workers/configuration/compatibility-dates/#strict-crypto-error-checking) compatibility flag to enable additional [Web Crypto API](/workers/runtime-apis/web-crypto/) error and security checking.
|
||||
- Fixes regression in the [TCP Sockets API](/workers/runtime-apis/tcp-sockets/) where `connect("google.com:443")` would fail with a `TypeError`.
|
||||
- publish_date: '2023-06-19'
|
||||
description: |-
|
||||
- The [TCP Sockets API](/workers/runtime-apis/tcp-sockets/) now reports clearer errors when a connection cannot be established.
|
||||
- Updated V8 to 11.5.
|
||||
- publish_date: '2023-06-09'
|
||||
description: |-
|
||||
- `AbortSignal.any()` is now available.
|
||||
- Updated V8 to 11.4.
|
||||
- Following an update to the [WHATWG URL spec](https://url.spec.whatwg.org/#interface-urlsearchparams), the `delete()` and `has()` methods of the `URLSearchParams` class now accept an optional second argument to specify the search parameter’s value. This is potentially a breaking change, so it is gated behind the new `urlsearchparams_delete_has_value_arg` and [`url_standard`](/workers/configuration/compatibility-dates/#new-url-parser-implementation) compatibility flags.
|
||||
- Added the [`strict_compression_checks`](/workers/configuration/compatibility-dates/#strict-compression-error-checking) compatibility flag for additional [`DecompressionStream`](/workers/runtime-apis/web-standards/#compression-streams) error checking.
|
||||
- publish_date: '2023-05-26'
|
||||
description: |-
|
||||
- A new [Hibernatable WebSockets API](/durable-objects/api/websockets/)
|
||||
(beta) has been added to [Durable Objects](/durable-objects/). The Hibernatable
|
||||
WebSockets API allows a Durable Object that is not currently running an event
|
||||
handler (for example, processing a WebSocket message or alarm) to be removed from
|
||||
memory while keeping its WebSockets connected (“hibernation”). A Durable Object
|
||||
that hibernates will not incur billable Duration (GB-sec) charges.
|
||||
- publish_date: '2023-05-16'
|
||||
description: |-
|
||||
- The [new `connect()` method](/workers/runtime-apis/tcp-sockets/) allows you to connect to any TCP-speaking services directly from your Workers. To learn more about other protocols supported on the Workers platform, visit the [new Protocols documentation](/workers/reference/protocols/).
|
||||
- We have added new [native database integrations](/workers/databases/native-integrations/) for popular serverless database providers, including Neon, PlanetScale, and Supabase. Native integrations automatically handle the process of creating a connection string and adding it as a Secret to your Worker.
|
||||
- You can now also connect directly to databases over TCP from a Worker, starting with [PostgreSQL](/hyperdrive/configuration/connect-to-postgres/). Support for PostgreSQL is based on the popular `pg` driver, and allows you to connect to any PostgreSQL instance over TLS from a Worker directly.
|
||||
- The [R2 Migrator](/r2/data-migration/) (Super Slurper), which automates the process of migrating from existing object storage providers to R2, is now Generally Available.
|
||||
- publish_date: '2023-05-15'
|
||||
description: |-
|
||||
- [Cursor](/workers/ai/), an experimental AI assistant, trained to answer
|
||||
questions about Cloudflare's Developer Platform, is now available to preview!
|
||||
Cursor can answer questions about Workers and the Cloudflare Developer Platform,
|
||||
and is itself built on Workers. You can read more about Cursor in the [announcement
|
||||
blog](https://blog.cloudflare.com/introducing-cursor-the-ai-assistant-for-docs/).
|
||||
- publish_date: '2023-05-12'
|
||||
description: |-
|
||||
- The [`performance.now()`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/now)
|
||||
and [`performance.timeOrigin`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)
|
||||
APIs can now be used in Cloudflare Workers. Just like `Date.now()`, for [security
|
||||
reasons](/workers/reference/security-model/) time only advances after I/O.
|
||||
- publish_date: '2023-05-05'
|
||||
description: |-
|
||||
- The new `nodeJsCompatModule` type can be used with a Worker bundle to emulate a Node.js environment. Common Node.js globals such as `process` and `Buffer` will be present, and `require('...')` can be used to load Node.js built-ins without the `node:` specifier prefix.
|
||||
- Fixed an issue where websocket connections would be disconnected when updating workers. Now, only websockets connected to Durable Object instances are disconnected by updates to that Durable Object’s code.
|
||||
- publish_date: '2023-04-28'
|
||||
description: |-
|
||||
- The Web Crypto API now supports curves Ed25519 and X25519 defined in the Secure Curves specification.
|
||||
- The global `connect` method has been moved to a `cloudflare:sockets` module.
|
||||
- publish_date: '2023-04-14'
|
||||
description: |-
|
||||
- No externally-visible changes this week.
|
||||
- publish_date: '2023-04-10'
|
||||
description: |-
|
||||
- `URL.canParse(...)` is a new standard API for testing that an input string can be parsed successfully as a URL without the additional cost of creating and throwing an error.
|
||||
- The Workers-specific `IdentityTransformStream` and `FixedLengthStream` classes now support specifying a `highWaterMark` for the writable-side that is used for backpressure signaling using the standard `writer.desiredSize`/`writer.ready` mechanisms.
|
||||
- publish_date: '2023-03-24'
|
||||
description: |-
|
||||
- Fixed a bug in Wrangler tail and live logs on the dashboard that
|
||||
prevented the Administrator Read-Only and Workers Tail Read roles from successfully
|
||||
tailing Workers.
|
||||
- publish_date: '2023-03-09'
|
||||
description: |-
|
||||
- No externally-visible changes.
|
||||
- publish_date: '2023-03-06'
|
||||
description: |-
|
||||
- [Workers Logpush](/workers/observability/logging/logpush/#limits) now supports
|
||||
300 characters per log line. This is an increase from the previous limit of 150
|
||||
characters per line.
|
||||
- publish_date: '2023-02-06'
|
||||
description: |-
|
||||
- Fixed a bug where transferring large request bodies to a Durable Object was unexpectedly slow.
|
||||
- Previously, an error would be thrown when trying to access unimplemented standard `Request` and `Response` properties. Now those will be left as `undefined`.
|
||||
- publish_date: '2023-01-31'
|
||||
description: |-
|
||||
- The [`request.cf`](/workers/runtime-apis/request/#incomingrequestcfproperties) object now includes two additional properties, `tlsClientHelloLength` and `tlsClientRandom`.
|
||||
- publish_date: '2023-01-13'
|
||||
description: |-
|
||||
- Durable Objects can now use jurisdictions with `idFromName` via a new subnamespace API.
|
||||
- V8 updated to 10.9.
|
||||
- publish_date: "2024-08-19"
|
||||
description: |-
|
||||
- Workers now support the [`allow_custom_ports` compatibility flag](/workers/configuration/compatibility-dates/#allow-specifying-a-custom-port-when-making-a-subrequest-with-the-fetch-api) which enables using the `fetch()` calls to custom ports.
|
||||
- publish_date: "2024-08-15"
|
||||
description: |-
|
||||
- Updated v8 to version 12.8.
|
||||
- You can now use [`Promise.try()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/try) in Cloudflare Workers. Refer to [`tc39/proposal-promise-try`](https://github.com/tc39/proposal-promise-try) for more context on this API that has recently been added to the JavaScript language.
|
||||
- publish_date: "2024-08-14"
|
||||
description: |-
|
||||
- When using the `nodejs_compat_v2` compatibility flag, the `setImmediate(fn)` API from Node.js is now available at the global scope.
|
||||
- The `internal_writable_stream_abort_clears_queue` compatibility flag will ensure that certain `WritableStream` `abort()` operations are handled immediately rather than lazily, ensuring that the stream is appropriately aborted when the consumer of the stream is no longer active.
|
||||
- publish_date: "2024-07-19"
|
||||
description: |-
|
||||
- Workers with the [mTLS](/workers/runtime-apis/bindings/mtls/) binding now support [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/).
|
||||
- publish_date: "2024-07-18"
|
||||
description: |-
|
||||
- Added a new `truncated` flag to [Tail Worker](/workers/observability/logging/tail-workers/) events to indicate when the event buffer is full and events are being dropped.
|
||||
- publish_date: "2024-07-17"
|
||||
description: |-
|
||||
- Updated v8 to version 12.7.
|
||||
- publish_date: "2024-07-11"
|
||||
description: |-
|
||||
- Added community contributed tutorial on how to create [custom access control for files in R2 using D1 and Workers](/developer-spotlight/tutorials/custom-access-control-for-files/).
|
||||
- Added community contributed tutorial on how to [send form submissions using Astro and Resend](/developer-spotlight/tutorials/handle-form-submission-with-astro-resend/).
|
||||
- Added community contributed tutorial on how to [create a sitemap from Sanity CMS with Workers](/developer-spotlight/tutorials/create-sitemap-from-sanity-cms/).
|
||||
- publish_date: "2024-07-03"
|
||||
description: |-
|
||||
- The [`node:crypto`](/workers/runtime-apis/nodejs/crypto/) implementation now includes the scrypt(...) and scryptSync(...) APIs.
|
||||
- Workers now support the standard [EventSource](/workers/runtime-apis/eventsource/) API.
|
||||
- Fixed a bug where when writing to an HTTP Response body would sometimes hang when the client disconnected (and sometimes throw an exception). It will now always throw an exception.
|
||||
- publish_date: "2024-07-01"
|
||||
description: |-
|
||||
- When using [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/), you can now use [version overrides](/workers/configuration/versions-and-deployments/gradual-deployments/#version-overrides) to send a request to a specific version of your Worker.
|
||||
- publish_date: "2024-06-28"
|
||||
description: |-
|
||||
- Fixed a bug which caused `Date.now()` to return skewed results if called before the first I/O of the first request after a Worker first started up. The value returned would be offset backwards by the amount of CPU time spent starting the Worker (compiling and running global scope), making it seem like the first I/O (e.g. first fetch()) was slower than it really was. This skew had nothing to do with Spectre mitigations; it was simply a longstanding bug.
|
||||
- publish_date: "2024-06-24"
|
||||
description: |-
|
||||
- [Exceptions](/durable-objects/best-practices/error-handling) thrown from Durable Object internal operations and tunneled to the caller may now be populated with a `.retryable: true` property if the exception was likely due to a transient failure, or populated with an `.overloaded: true` property if the exception was due to [overload](/durable-objects/observability/troubleshooting/#durable-object-is-overloaded).
|
||||
- publish_date: "2024-06-20"
|
||||
description: |-
|
||||
- We now prompt for extra confirmation if attempting to rollback to a version of a Worker using the [Deployments API](/api/operations/worker-deployments-create-deployment) where the value of a secret is different than the currently deployed version. A `?force=true` query parameter can be specified to proceed with the rollback.
|
||||
- publish_date: "2024-06-19"
|
||||
description: |-
|
||||
- When using [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/), the `buffer` module now has an implementation of `isAscii()` and `isUtf8()` methods.
|
||||
- Fixed a bug where exceptions propagated from [JS RPC](/workers/runtime-apis/rpc) calls to Durable Objects would lack the `.remote` property that exceptions from `fetch()` calls to Durable Objects have.
|
||||
- publish_date: "2024-06-12"
|
||||
description: |-
|
||||
- Blob and Body objects now include a new `bytes()` method, reflecting [recent](https://w3c.github.io/FileAPI/#bytes-method-algo) [additions](https://fetch.spec.whatwg.org/#dom-body-bytes) to web standards.
|
||||
- publish_date: "2024-06-03"
|
||||
description: |-
|
||||
- Workers with [Smart Placement](/workers/configuration/smart-placement/) enabled now support [Gradual Deployments](/workers/configuration/versions-and-deployments/gradual-deployments/).
|
||||
- publish_date: "2024-05-17"
|
||||
description: |-
|
||||
- Updated v8 to version 12.6.
|
||||
- publish_date: "2024-05-15"
|
||||
description: |-
|
||||
- The new [`fetch_standard_url` compatibility flag](/workers/configuration/compatibility-dates/#use-standard-url-parsing-in-fetch) will become active by default on June 3rd, 2024 and ensures that URLs passed into the `fetch(...)` API, the `new Request(...)` constructor, and redirected requests will be parsed using the standard WHATWG URL parser.
|
||||
- DigestStream is now more efficient and exposes a new `bytesWritten` property that indicates that number of bytes written to the digest.
|
||||
- publish_date: "2024-05-13"
|
||||
description: |-
|
||||
- Updated v8 to version 12.5.
|
||||
- A bug in the fetch API implementation would cause the content type of a Blob to be incorrectly set. The fix is being released behind a new [`blob_standard_mime_type` compatibility flag](/workers/configuration/compatibility-dates/#properly-extract-blob-mime-type-from-content-type-headers).
|
||||
- publish_date: "2024-05-03"
|
||||
description: |-
|
||||
- Fixed RPC to/from Durable Objects not honoring the output gate.
|
||||
- The `internal_stream_byob_return_view` compatibility flag can be used to improve the standards compliance of the `ReadableStreamBYOBReader` implementation when working with BYOB streams provided by the runtime (like in `response.body` or `request.body`). The flag ensures that the final read result will always include a `value` field whose value is set to an empty `Uint8Array` whose underlying `ArrayBuffer` is the same memory allocation as the one passed in on the call to `read()`.
|
||||
- The Web platform standard `reportError(err)` global API is now available in workers. The reported error will first be emitted as an 'error' event on the global scope then reported in both the console output and tail worker exceptions by default.
|
||||
- publish_date: "2024-04-26"
|
||||
description: |-
|
||||
- Updated v8 to version 12.4.
|
||||
- publish_date: "2024-04-11"
|
||||
description: |-
|
||||
- Improve Streams API spec compliance by exposing `desiredSize` and other properties on stream class prototypes
|
||||
- The new `URL.parse(...)` method is implemented. This provides an alternative to the URL constructor that does not throw exceptions on invalid URLs.
|
||||
- R2 bindings objects now have a `storageClass` option. This can be set on object upload to specify the R2 storage class - Standard or Infrequent Access. The property is also returned with object metadata.
|
||||
- publish_date: "2024-04-05"
|
||||
description: |-
|
||||
- A new [JavaScript-native remote procedure call (RPC) API](/workers/runtime-apis/rpc) is now available, allowing you to communicate more easily across Workers and between Workers and Durable Objects.
|
||||
- publish_date: "2024-04-04"
|
||||
description: |-
|
||||
- There is no longer an explicit limit on the total amount of data which may be uploaded with Cache API [`put()`](/workers/runtime-apis/cache/#put) per request. Other [Cache API Limits](/workers/platform/limits/#cache-api-limits) continue to apply.
|
||||
- The Web standard `ReadableStream.from()` API is now implemented. The API enables creating a `ReadableStream` from a either a sync or async iterable.
|
||||
- publish_date: "2024-04-03"
|
||||
description: |-
|
||||
- When the [`brotli_content_encoding`](/workers/configuration/compatibility-dates/#brotli-content-encoding-support) compatibility flag is enabled, the Workers runtime now supports compressing and decompressing request bodies encoded using the [Brotli](https://developer.mozilla.org/en-US/docs/Glossary/Brotli_compression) compression algorithm. Refer to [this docs section](/workers/runtime-apis/fetch/#how-the-accept-encoding-header-is-handled) for more detail.
|
||||
- publish_date: "2024-04-02"
|
||||
description: |-
|
||||
- You can now [write Workers in Python](/workers/languages/python)
|
||||
- publish_date: "2024-04-01"
|
||||
description: |-
|
||||
- The new [`unwrap_custom_thenables` compatibility flag](/workers/configuration/compatibility-dates/#handling-custom-thenables) enables workers to accept custom thenables in internal APIs that expect a promise (for instance, the `ctx.waitUntil(...)` method).
|
||||
- TransformStreams created with the TransformStream constructor now have a cancel algorithm that is called when the stream is canceled or aborted. This change is part of the implementation of the WHATWG Streams standard.
|
||||
- The [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/) now includes an implementation of the [`MockTracker` API from `node:test`](https://nodejs.org/api/test.html#class-mocktracker). This is not an implementation of the full `node:test` module, and mock timers are currently not included.
|
||||
- Exceptions reported to [Tail Workers](/workers/observability/logging/tail-workers/) now include a "stack" property containing the exception's stack trace, if available.
|
||||
- publish_date: "2024-03-11"
|
||||
description: |-
|
||||
- Built-in APIs that return Promises will now produce stack traces when the Promise rejects. Previously, the rejection error lacked a stack trace.
|
||||
- A new compat flag `fetcher_no_get_put_delete` removes the `get()`, `put()`, and `delete()` methods on service bindings and Durable Object stubs. This will become the default as of compatibility date 2024-03-26. These methods were designed as simple convenience wrappers around `fetch()`, but were never documented.
|
||||
- Updated v8 to version 12.3.
|
||||
- publish_date: "2024-02-24"
|
||||
description: |-
|
||||
- v8 updated to version 12.2.
|
||||
- You can now use [Iterator helpers](https://v8.dev/features/iterator-helpers) in Workers.
|
||||
- You can now use [new methods on `Set`](https://github.com/tc39/proposal-set-methods), such as `Set.intersection` and `Set.union`, in Workers.
|
||||
- publish_date: "2024-02-23"
|
||||
description: |-
|
||||
- Sockets now support an [`opened`](/workers/runtime-apis/tcp-sockets/#socket) attribute.
|
||||
- [Durable Object alarm handlers](/durable-objects/api/alarms/#alarm) now impose a maximum wall time of 15 minutes.
|
||||
- publish_date: "2023-12-04"
|
||||
description: |-
|
||||
- The Web Platform standard [`navigator.sendBeacon(...)` API](/workers/runtime-apis/web-standards#navigatorsendbeaconurl-data) is now provided by the Workers runtime.
|
||||
- V8 updated to 12.0.
|
||||
- publish_date: "2023-10-30"
|
||||
description: |-
|
||||
- A new usage model called [Workers Standard](/workers/platform/pricing/#workers) is available for Workers and Pages Functions pricing. This is now the default usage model for accounts that are first upgraded to the Workers Paid plan. Read the [blog post](https://blog.cloudflare.com/workers-pricing-scale-to-zero/) for more information.
|
||||
- The usage model set in a script's wrangler.toml will be ignored after an account has opted-in to [Workers Standard](/workers/platform/pricing/#workers) pricing. It must be configured through the dashboard (Workers & Pages > Select your Worker > Settings > Usage Model).
|
||||
- Workers and Pages Functions on the Standard usage model can set custom [CPU limits](/workers/wrangler/configuration/#limits) for their Workers
|
||||
- publish_date: "2023-10-20"
|
||||
description: |-
|
||||
- Added the [`crypto_preserve_public_exponent`](/workers/configuration/compatibility-dates/#webcrypto-preserve-publicexponent-field)
|
||||
compatibility flag to correct a wrong type being used in the algorithm field of RSA keys in
|
||||
the WebCrypto API.
|
||||
- publish_date: "2023-10-18"
|
||||
description: |-
|
||||
- The limit of 3 Cron Triggers per Worker has been removed. Account-level limits on the total number of
|
||||
Cron Triggers across all Workers still apply.
|
||||
- publish_date: "2023-10-12"
|
||||
description: |-
|
||||
- A [TCP Socket](/workers/runtime-apis/tcp-sockets/)'s WritableStream now ensures the connection has opened before resolving the promise returned by `close`.
|
||||
- publish_date: "2023-10-09"
|
||||
description: |-
|
||||
- The Web Platform standard [`CustomEvent` class](https://dom.spec.whatwg.org/#interface-customevent) is now available in Workers.
|
||||
- Fixed a bug in the WebCrypto API where the `publicExponent` field of the algorithm of RSA keys would have the wrong type. Use the [`crypto_preserve_public_exponent` compatibility flag](/workers/configuration/compatibility-dates/#webcrypto-preserve-publicexponent-field) to enable the new behavior.
|
||||
- publish_date: "2023-09-14"
|
||||
description: |-
|
||||
- An implementation of the [`node:crypto`](/workers/runtime-apis/nodejs/crypto/)
|
||||
API from Node.js is now available when the [`nodejs_compat` compatibility flag](/workers/runtime-apis/nodejs/)
|
||||
is enabled.
|
||||
- publish_date: "2023-07-14"
|
||||
description: |-
|
||||
- An implementation of the [`util.MIMEType`](https://nodejs.org/api/util.html#class-utilmimetype)
|
||||
API from Node.js is now available when the [`nodejs_compat` compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/)
|
||||
is enabled.
|
||||
- publish_date: "2023-07-07"
|
||||
description: |-
|
||||
- An implementation of the [`process.env`](/workers/runtime-apis/nodejs/process) API from Node.js is now available when using the `nodejs_compat` compatibility flag.
|
||||
- An implementation of the [`diagnostics_channel`](/workers/runtime-apis/nodejs/diagnostics-channel) API from Node.js is now available when using the `nodejs_compat` compatibility flag.
|
||||
- publish_date: "2023-06-22"
|
||||
description: |-
|
||||
- Added the [`strict_crypto_checks`](/workers/configuration/compatibility-dates/#strict-crypto-error-checking) compatibility flag to enable additional [Web Crypto API](/workers/runtime-apis/web-crypto/) error and security checking.
|
||||
- Fixes regression in the [TCP Sockets API](/workers/runtime-apis/tcp-sockets/) where `connect("google.com:443")` would fail with a `TypeError`.
|
||||
- publish_date: "2023-06-19"
|
||||
description: |-
|
||||
- The [TCP Sockets API](/workers/runtime-apis/tcp-sockets/) now reports clearer errors when a connection cannot be established.
|
||||
- Updated V8 to 11.5.
|
||||
- publish_date: "2023-06-09"
|
||||
description: |-
|
||||
- `AbortSignal.any()` is now available.
|
||||
- Updated V8 to 11.4.
|
||||
- Following an update to the [WHATWG URL spec](https://url.spec.whatwg.org/#interface-urlsearchparams), the `delete()` and `has()` methods of the `URLSearchParams` class now accept an optional second argument to specify the search parameter’s value. This is potentially a breaking change, so it is gated behind the new `urlsearchparams_delete_has_value_arg` and [`url_standard`](/workers/configuration/compatibility-dates/#new-url-parser-implementation) compatibility flags.
|
||||
- Added the [`strict_compression_checks`](/workers/configuration/compatibility-dates/#strict-compression-error-checking) compatibility flag for additional [`DecompressionStream`](/workers/runtime-apis/web-standards/#compression-streams) error checking.
|
||||
- publish_date: "2023-05-26"
|
||||
description: |-
|
||||
- A new [Hibernatable WebSockets API](/durable-objects/api/websockets/)
|
||||
(beta) has been added to [Durable Objects](/durable-objects/). The Hibernatable
|
||||
WebSockets API allows a Durable Object that is not currently running an event
|
||||
handler (for example, processing a WebSocket message or alarm) to be removed from
|
||||
memory while keeping its WebSockets connected (“hibernation”). A Durable Object
|
||||
that hibernates will not incur billable Duration (GB-sec) charges.
|
||||
- publish_date: "2023-05-16"
|
||||
description: |-
|
||||
- The [new `connect()` method](/workers/runtime-apis/tcp-sockets/) allows you to connect to any TCP-speaking services directly from your Workers. To learn more about other protocols supported on the Workers platform, visit the [new Protocols documentation](/workers/reference/protocols/).
|
||||
- We have added new [native database integrations](/workers/databases/native-integrations/) for popular serverless database providers, including Neon, PlanetScale, and Supabase. Native integrations automatically handle the process of creating a connection string and adding it as a Secret to your Worker.
|
||||
- You can now also connect directly to databases over TCP from a Worker, starting with [PostgreSQL](/hyperdrive/configuration/connect-to-postgres/). Support for PostgreSQL is based on the popular `pg` driver, and allows you to connect to any PostgreSQL instance over TLS from a Worker directly.
|
||||
- The [R2 Migrator](/r2/data-migration/) (Super Slurper), which automates the process of migrating from existing object storage providers to R2, is now Generally Available.
|
||||
- publish_date: "2023-05-15"
|
||||
description: |-
|
||||
- [Cursor](/workers/ai/), an experimental AI assistant, trained to answer
|
||||
questions about Cloudflare's Developer Platform, is now available to preview!
|
||||
Cursor can answer questions about Workers and the Cloudflare Developer Platform,
|
||||
and is itself built on Workers. You can read more about Cursor in the [announcement
|
||||
blog](https://blog.cloudflare.com/introducing-cursor-the-ai-assistant-for-docs/).
|
||||
- publish_date: "2023-05-12"
|
||||
description: |-
|
||||
- The [`performance.now()`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/now)
|
||||
and [`performance.timeOrigin`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/timeOrigin)
|
||||
APIs can now be used in Cloudflare Workers. Just like `Date.now()`, for [security
|
||||
reasons](/workers/reference/security-model/) time only advances after I/O.
|
||||
- publish_date: "2023-05-05"
|
||||
description: |-
|
||||
- The new `nodeJsCompatModule` type can be used with a Worker bundle to emulate a Node.js environment. Common Node.js globals such as `process` and `Buffer` will be present, and `require('...')` can be used to load Node.js built-ins without the `node:` specifier prefix.
|
||||
- Fixed an issue where websocket connections would be disconnected when updating workers. Now, only websockets connected to Durable Object instances are disconnected by updates to that Durable Object’s code.
|
||||
- publish_date: "2023-04-28"
|
||||
description: |-
|
||||
- The Web Crypto API now supports curves Ed25519 and X25519 defined in the Secure Curves specification.
|
||||
- The global `connect` method has been moved to a `cloudflare:sockets` module.
|
||||
- publish_date: "2023-04-14"
|
||||
description: |-
|
||||
- No externally-visible changes this week.
|
||||
- publish_date: "2023-04-10"
|
||||
description: |-
|
||||
- `URL.canParse(...)` is a new standard API for testing that an input string can be parsed successfully as a URL without the additional cost of creating and throwing an error.
|
||||
- The Workers-specific `IdentityTransformStream` and `FixedLengthStream` classes now support specifying a `highWaterMark` for the writable-side that is used for backpressure signaling using the standard `writer.desiredSize`/`writer.ready` mechanisms.
|
||||
- publish_date: "2023-03-24"
|
||||
description: |-
|
||||
- Fixed a bug in Wrangler tail and live logs on the dashboard that
|
||||
prevented the Administrator Read-Only and Workers Tail Read roles from successfully
|
||||
tailing Workers.
|
||||
- publish_date: "2023-03-09"
|
||||
description: |-
|
||||
- No externally-visible changes.
|
||||
- publish_date: "2023-03-06"
|
||||
description: |-
|
||||
- [Workers Logpush](/workers/observability/logging/logpush/#limits) now supports
|
||||
300 characters per log line. This is an increase from the previous limit of 150
|
||||
characters per line.
|
||||
- publish_date: "2023-02-06"
|
||||
description: |-
|
||||
- Fixed a bug where transferring large request bodies to a Durable Object was unexpectedly slow.
|
||||
- Previously, an error would be thrown when trying to access unimplemented standard `Request` and `Response` properties. Now those will be left as `undefined`.
|
||||
- publish_date: "2023-01-31"
|
||||
description: |-
|
||||
- The [`request.cf`](/workers/runtime-apis/request/#incomingrequestcfproperties) object now includes two additional properties, `tlsClientHelloLength` and `tlsClientRandom`.
|
||||
- publish_date: "2023-01-13"
|
||||
description: |-
|
||||
- Durable Objects can now use jurisdictions with `idFromName` via a new subnamespace API.
|
||||
- V8 updated to 10.9.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ entries:
|
|||
* **Consent Management**: Support styling the Consent Modal when CSP is enabled
|
||||
* **Consent Management**: Fix an issue that could cause tools to load before consent was granted when TCF is enabled
|
||||
* **Zaraz Debugger**: Remove redundant messages related to empty values
|
||||
* **Amplitude Managed Component**: Respect the EU endpoint setting
|
||||
* **Amplitude Managed Component**: Respect the EU endpoint setting
|
||||
- publish_date: '2024-08-23'
|
||||
description: |
|
||||
* **Automatic Actions**: Automatic Event Tracking is now fully available
|
||||
|
|
@ -23,7 +23,7 @@ entries:
|
|||
* **Automatic Actions**: Automatic Pageview tracking is now fully available
|
||||
* **Google Analytics 4**: Support Google Consent signals when using e-commerce tracking
|
||||
* **HTTP Events API**: Ignore bot score detection on the HTTP Events API endpoint
|
||||
* **Zaraz Debugger**: Show client-side network requests initiated by Managed Components
|
||||
* **Zaraz Debugger**: Show client-side network requests initiated by Managed Components
|
||||
- publish_date: '2024-08-12'
|
||||
description: |
|
||||
* **Automatic Actions**: New tools now support Automatic Pageview tracking
|
||||
|
|
@ -76,7 +76,7 @@ entries:
|
|||
* **Bugfix**: Prevent duplicate pageviews in monitoring after consent granting
|
||||
* **Bugfix**: Prevent Managed Component routes from blocking origin routes unintentionally
|
||||
- publish_date: '2024-02-15'
|
||||
|
||||
|
||||
description: |-
|
||||
* **Single Page Applications**: Introduce `zaraz.spaPageview()` for manually triggering SPA pageviews
|
||||
* **Pinterest Managed Component**: Add ecommerce support
|
||||
|
|
|
|||
|
|
@ -1,26 +1,26 @@
|
|||
---
|
||||
productName: API Shield
|
||||
entries:
|
||||
- term: API call
|
||||
general_definition: |-
|
||||
Also known as an API request. An API call is a message sent to a server asking an API to provide a service or information.
|
||||
- term: API call
|
||||
general_definition: |-
|
||||
Also known as an API request. An API call is a message sent to a server asking an API to provide a service or information.
|
||||
|
||||
- term: API endpoint
|
||||
general_definition: |-
|
||||
The API endpoint is the location where API calls or requests are fulfilled. API Shield defines endpoints as a host, method, and path tuple.
|
||||
- term: API endpoint
|
||||
general_definition: |-
|
||||
The API endpoint is the location where API calls or requests are fulfilled. API Shield defines endpoints as a host, method, and path tuple.
|
||||
|
||||
- term: API schema
|
||||
general_definition: |-
|
||||
The API schema defines which API requests are valid based on several request properties like target endpoint, path or query variable format, and HTTP method.
|
||||
- term: API schema
|
||||
general_definition: |-
|
||||
The API schema defines which API requests are valid based on several request properties like target endpoint, path or query variable format, and HTTP method.
|
||||
|
||||
- term: session identifier
|
||||
general_definition: |-
|
||||
A session identifier is a unique number that a website assigns to identify a specific user for the duration of their visit.
|
||||
|
||||
- term: source endpoint
|
||||
general_definition: |-
|
||||
The source endpoint is the endpoint managed by API Shield in Endpoint Management by its routing feature.
|
||||
- term: session identifier
|
||||
general_definition: |-
|
||||
A session identifier is a unique number that a website assigns to identify a specific user for the duration of their visit.
|
||||
|
||||
- term: target endpoint
|
||||
general_definition: |-
|
||||
The target endpoint is the ultimate destination that a request is sent to by API Shield's routing feature.
|
||||
- term: source endpoint
|
||||
general_definition: |-
|
||||
The source endpoint is the endpoint managed by API Shield in Endpoint Management by its routing feature.
|
||||
|
||||
- term: target endpoint
|
||||
general_definition: |-
|
||||
The target endpoint is the ultimate destination that a request is sent to by API Shield's routing feature.
|
||||
|
|
|
|||
|
|
@ -1,30 +1,30 @@
|
|||
---
|
||||
productName: Bots
|
||||
entries:
|
||||
- term: bot
|
||||
general_definition: |-
|
||||
A software application programmed to do tasks that can be used for good (chatbots, search engine crawlers) or for evil (inventory hoarding, credential stuffing).
|
||||
- term: bot
|
||||
general_definition: |-
|
||||
A software application programmed to do tasks that can be used for good (chatbots, search engine crawlers) or for evil (inventory hoarding, credential stuffing).
|
||||
|
||||
- term: bot score
|
||||
general_definition: |-
|
||||
A score from 1 to 99 that indicates how likely that request came from a bot, in which 1 to 29 is likely automated and 30 to 99 is likely human.
|
||||
- term: bot score
|
||||
general_definition: |-
|
||||
A score from 1 to 99 that indicates how likely that request came from a bot, in which 1 to 29 is likely automated and 30 to 99 is likely human.
|
||||
|
||||
- term: bot tags
|
||||
general_definition: |-
|
||||
Additional information about a bot request, such as why Cloudflare has given it a bot score and whether the request came from a verified bot or a category of verified bots.
|
||||
- term: bot tags
|
||||
general_definition: |-
|
||||
Additional information about a bot request, such as why Cloudflare has given it a bot score and whether the request came from a verified bot or a category of verified bots.
|
||||
|
||||
- term: Challenge Solve Rate (CSR)
|
||||
general_definition: |-
|
||||
The percentage of issued challenges that were solved.
|
||||
- term: Challenge Solve Rate (CSR)
|
||||
general_definition: |-
|
||||
The percentage of issued challenges that were solved.
|
||||
|
||||
- term: detection ID
|
||||
general_definition: |-
|
||||
Static rules that are used to detect predictable bot behavior with no overlap with human traffic.
|
||||
- term: detection ID
|
||||
general_definition: |-
|
||||
Static rules that are used to detect predictable bot behavior with no overlap with human traffic.
|
||||
|
||||
- term: JA3 fingerprint
|
||||
general_definition: |-
|
||||
JA3 and JA4 fingerprints profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
|
||||
- term: JA3 fingerprint
|
||||
general_definition: |-
|
||||
JA3 and JA4 fingerprints profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
|
||||
|
||||
- term: verified bot
|
||||
general_definition: |-
|
||||
Bots that are transparent about who they are and what they do.
|
||||
- term: verified bot
|
||||
general_definition: |-
|
||||
Bots that are transparent about who they are and what they do.
|
||||
|
|
|
|||
|
|
@ -1,28 +1,28 @@
|
|||
---
|
||||
productName: BYOIP
|
||||
entries:
|
||||
- term: address map
|
||||
general_definition: |-
|
||||
a data structure enabling customers with BYOIP prefixes or account-level static IPs to specify which IP addresses should be mapped to DNS records when they are proxied through Cloudflare.
|
||||
- term: address map
|
||||
general_definition: |-
|
||||
a data structure enabling customers with BYOIP prefixes or account-level static IPs to specify which IP addresses should be mapped to DNS records when they are proxied through Cloudflare.
|
||||
|
||||
- term: autonomous system numbers (ASNs)
|
||||
general_definition: |-
|
||||
a large network or group of networks that has a unified routing policy. Every computer or device that connects to the Internet is connected to an autonomous system.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
- term: autonomous system numbers (ASNs)
|
||||
general_definition: |-
|
||||
a large network or group of networks that has a unified routing policy. Every computer or device that connects to the Internet is connected to an autonomous system.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
|
||||
- term: Border Gateway Protocol (BGP)
|
||||
general_definition: |-
|
||||
the routing protocol for the Internet, which is responsible for picking the most efficient routes to deliver Internet traffic.
|
||||
- term: Border Gateway Protocol (BGP)
|
||||
general_definition: |-
|
||||
the routing protocol for the Internet, which is responsible for picking the most efficient routes to deliver Internet traffic.
|
||||
|
||||
- term: Internet Routing Registry (IRR)
|
||||
general_definition: |-
|
||||
a globally distributed database of routing information which contains announced routes and routing policies in a common format. Network operators use this information to configure backbone routers.
|
||||
- term: Internet Routing Registry (IRR)
|
||||
general_definition: |-
|
||||
a globally distributed database of routing information which contains announced routes and routing policies in a common format. Network operators use this information to configure backbone routers.
|
||||
|
||||
- term: Resource Public Key Infrastructure (RPKI)
|
||||
general_definition: |-
|
||||
a cryptographic method of signing records that associate a route with an originating autonomous system number.
|
||||
- term: Resource Public Key Infrastructure (RPKI)
|
||||
general_definition: |-
|
||||
a cryptographic method of signing records that associate a route with an originating autonomous system number.
|
||||
|
||||
- term: Unicast Reverse Path Forwarding (uRPF)
|
||||
general_definition: |-
|
||||
a security feature that can prevent spoofing attacks.
|
||||
- term: Unicast Reverse Path Forwarding (uRPF)
|
||||
general_definition: |-
|
||||
a security feature that can prevent spoofing attacks.
|
||||
|
|
|
|||
|
|
@ -1,78 +1,78 @@
|
|||
---
|
||||
productName: Cache
|
||||
entries:
|
||||
- term: cached bandwidth (cached egress bandwidth)
|
||||
general_definition: |-
|
||||
the amount of bandwidth served from Cloudflare without hitting the origin server. Cached bandwidth is the sum of all `EdgeResponseBytes` where `CacheCacheStatus` equals `hit`, `stale`, `updating`, `ignored`, or `revalidated`.
|
||||
- term: cached bandwidth (cached egress bandwidth)
|
||||
general_definition: |-
|
||||
the amount of bandwidth served from Cloudflare without hitting the origin server. Cached bandwidth is the sum of all `EdgeResponseBytes` where `CacheCacheStatus` equals `hit`, `stale`, `updating`, `ignored`, or `revalidated`.
|
||||
|
||||
- term: cached requests
|
||||
general_definition: |-
|
||||
the number of requests served from Cloudflare without having to hit the origin server. Cached requests are the sum of all requests where `CacheCacheStatus` equals `hit`, `stale`, `updating`, `ignored`. This does not include `revalidated` since the request had to be sent to the origin server.
|
||||
- term: cached requests
|
||||
general_definition: |-
|
||||
the number of requests served from Cloudflare without having to hit the origin server. Cached requests are the sum of all requests where `CacheCacheStatus` equals `hit`, `stale`, `updating`, `ignored`. This does not include `revalidated` since the request had to be sent to the origin server.
|
||||
|
||||
- term: dynamic content
|
||||
general_definition: |-
|
||||
dynamic content refers to website content that changes based on factors specific to the user such as time of visit, location, and device. News websites or social media are examples of this type of content. For this type of website, content has to be fetched from the origin server every time it is requested.
|
||||
- term: dynamic content
|
||||
general_definition: |-
|
||||
dynamic content refers to website content that changes based on factors specific to the user such as time of visit, location, and device. News websites or social media are examples of this type of content. For this type of website, content has to be fetched from the origin server every time it is requested.
|
||||
|
||||
- term: origin bandwidth (origin egress bandwidth)
|
||||
general_definition: |-
|
||||
the amount of data transferred from the origin server to Cloudflare within a certain period of time. Origin bandwidth is the sum of all `EdgeResponseBytes` where `OriginResponseStatus` does not equal `0`.
|
||||
- term: origin bandwidth (origin egress bandwidth)
|
||||
general_definition: |-
|
||||
the amount of data transferred from the origin server to Cloudflare within a certain period of time. Origin bandwidth is the sum of all `EdgeResponseBytes` where `OriginResponseStatus` does not equal `0`.
|
||||
|
||||
- term: saved bandwidth (saved egress bandwidth)
|
||||
general_definition: |-
|
||||
the percentage of bandwidth saved by caching on the Cloudflare network.
|
||||
- term: saved bandwidth (saved egress bandwidth)
|
||||
general_definition: |-
|
||||
the percentage of bandwidth saved by caching on the Cloudflare network.
|
||||
|
||||
- term: static content
|
||||
general_definition: |-
|
||||
static content, like images, stylesheets, and JavaScript, remains the same for all users. It can be directly served from the cache without fetching from the origin server because it does not change without manual intervention.
|
||||
- term: static content
|
||||
general_definition: |-
|
||||
static content, like images, stylesheets, and JavaScript, remains the same for all users. It can be directly served from the cache without fetching from the origin server because it does not change without manual intervention.
|
||||
|
||||
- term: uncached requests
|
||||
general_definition: |-
|
||||
uncached requests are requests that are not cached and therefore are served from the origin server. Uncached requests are the sum of all requests where `CacheCacheStatus` does not equal to `hit`, `stale`, `updating`, or `ignored`.
|
||||
- term: uncached requests
|
||||
general_definition: |-
|
||||
uncached requests are requests that are not cached and therefore are served from the origin server. Uncached requests are the sum of all requests where `CacheCacheStatus` does not equal to `hit`, `stale`, `updating`, or `ignored`.
|
||||
|
||||
- term: uncached bandwidth (uncached egress bandwidth)
|
||||
general_definition: |-
|
||||
uncached bandwidth is the amount of bandwidth that is not cached and therefore is served from the origin. Uncached bandwidth is the sum of all `EdgeResponseBytes` where `CacheCacheStatus` does not equal `hit`, `stale`, `updating`, `ignored`, or `revalidated`.
|
||||
- term: uncached bandwidth (uncached egress bandwidth)
|
||||
general_definition: |-
|
||||
uncached bandwidth is the amount of bandwidth that is not cached and therefore is served from the origin. Uncached bandwidth is the sum of all `EdgeResponseBytes` where `CacheCacheStatus` does not equal `hit`, `stale`, `updating`, `ignored`, or `revalidated`.
|
||||
|
||||
- term: cache
|
||||
general_definition: |-
|
||||
a temporary storage area where frequently accessed data is stored for quick retrieval.
|
||||
- term: cache
|
||||
general_definition: |-
|
||||
a temporary storage area where frequently accessed data is stored for quick retrieval.
|
||||
|
||||
- term: caching
|
||||
general_definition: |-
|
||||
the process of storing copies of files or data in a cache to accelerate future requests.
|
||||
- term: caching
|
||||
general_definition: |-
|
||||
the process of storing copies of files or data in a cache to accelerate future requests.
|
||||
|
||||
- term: edge server
|
||||
general_definition: |-
|
||||
a server located at the edge of a network, typically within a CDN, that serves content to end-users.
|
||||
associated_products:
|
||||
- Logs
|
||||
- term: edge server
|
||||
general_definition: |-
|
||||
a server located at the edge of a network, typically within a CDN, that serves content to end-users.
|
||||
associated_products:
|
||||
- Logs
|
||||
|
||||
- term: origin server
|
||||
general_definition: |-
|
||||
the original server where the web content is hosted before it is distributed to edge servers in a CDN.
|
||||
- term: origin server
|
||||
general_definition: |-
|
||||
the original server where the web content is hosted before it is distributed to edge servers in a CDN.
|
||||
|
||||
- term: cache hit
|
||||
general_definition: |-
|
||||
when a requested piece of content is found in the cache, reducing the need to fetch it from the origin server.
|
||||
- term: cache hit
|
||||
general_definition: |-
|
||||
when a requested piece of content is found in the cache, reducing the need to fetch it from the origin server.
|
||||
|
||||
- term: cache miss
|
||||
general_definition: |-
|
||||
when a requested piece of content is not found in the cache, requiring the server to fetch it from the origin server.
|
||||
- term: cache miss
|
||||
general_definition: |-
|
||||
when a requested piece of content is not found in the cache, requiring the server to fetch it from the origin server.
|
||||
|
||||
- term: purge
|
||||
general_definition: |-
|
||||
the process of removing outdated content from the cache to make room for updated content and ensure the delivery of the latest content.
|
||||
- term: purge
|
||||
general_definition: |-
|
||||
the process of removing outdated content from the cache to make room for updated content and ensure the delivery of the latest content.
|
||||
|
||||
- term: time-to-live (TTL)
|
||||
general_definition: |-
|
||||
the duration for which a cached copy of a resource is considered valid before it needs to be refreshed or revalidated.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
- term: time-to-live (TTL)
|
||||
general_definition: |-
|
||||
the duration for which a cached copy of a resource is considered valid before it needs to be refreshed or revalidated.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
|
||||
- term: cache lock
|
||||
general_definition: |-
|
||||
cache lock (or mutex) is a mechanism employed by CDN data centers, comprising numerous servers, to prevent the overloading of origin servers. This mechanism ensures that only one server can request a specific file from the origin at any given time, facilitating efficient coordination among the servers.
|
||||
- term: cache lock
|
||||
general_definition: |-
|
||||
cache lock (or mutex) is a mechanism employed by CDN data centers, comprising numerous servers, to prevent the overloading of origin servers. This mechanism ensures that only one server can request a specific file from the origin at any given time, facilitating efficient coordination among the servers.
|
||||
|
||||
- term: total bandwidth (total egress bandwidth, edge bandwidth)
|
||||
general_definition: |-
|
||||
total bandwidth is the amount of data transferred from Cloudflare to end users within a certain period of time. Total bandwidth equals the sum of all `EdgeResponseBytes` for a certain period of time.
|
||||
- term: total bandwidth (total egress bandwidth, edge bandwidth)
|
||||
general_definition: |-
|
||||
total bandwidth is the amount of data transferred from Cloudflare to end users within a certain period of time. Total bandwidth equals the sum of all `EdgeResponseBytes` for a certain period of time.
|
||||
|
|
|
|||
|
|
@ -1,252 +1,252 @@
|
|||
---
|
||||
productName: Cloudflare One
|
||||
entries:
|
||||
- term: Access group
|
||||
general_definition: |-
|
||||
a set of rules that can be configured once and then quickly applied across many Access applications.
|
||||
- term: Access group
|
||||
general_definition: |-
|
||||
a set of rules that can be configured once and then quickly applied across many Access applications.
|
||||
|
||||
- term: App Launcher
|
||||
general_definition: |-
|
||||
the App Launcher portal provides end users with a single dashboard to open applications secured by Cloudflare Zero Trust.
|
||||
- term: App Launcher
|
||||
general_definition: |-
|
||||
the App Launcher portal provides end users with a single dashboard to open applications secured by Cloudflare Zero Trust.
|
||||
|
||||
- term: application
|
||||
general_definition: |-
|
||||
the resource protected by Cloudflare Zero Trust, which can be a subdomain, a path, or a SaaS application.
|
||||
- term: application
|
||||
general_definition: |-
|
||||
the resource protected by Cloudflare Zero Trust, which can be a subdomain, a path, or a SaaS application.
|
||||
|
||||
- term: application token
|
||||
general_definition: |-
|
||||
a piece of data that grants a user access to a specific Access application for a period of time. Can be stored in a browser cookie or passed to the application in place of a normal password.
|
||||
- term: application token
|
||||
general_definition: |-
|
||||
a piece of data that grants a user access to a specific Access application for a period of time. Can be stored in a browser cookie or passed to the application in place of a normal password.
|
||||
|
||||
- term: captive portal
|
||||
general_definition: |-
|
||||
a login screen shown to users when they connect to a public Wi-Fi. Captive portals typically occur in places such as airports, cafes, and hotels.
|
||||
- term: captive portal
|
||||
general_definition: |-
|
||||
a login screen shown to users when they connect to a public Wi-Fi. Captive portals typically occur in places such as airports, cafes, and hotels.
|
||||
|
||||
- term: CGNAT IP
|
||||
general_definition: |-
|
||||
a unique, virtual IP address assigned to each WARP device from the `100.96.0.0/12` range. You can view the CGNAT IP for a device on its **My Team** > **Devices** page.
|
||||
- term: CGNAT IP
|
||||
general_definition: |-
|
||||
a unique, virtual IP address assigned to each WARP device from the `100.96.0.0/12` range. You can view the CGNAT IP for a device on its **My Team** > **Devices** page.
|
||||
|
||||
- term: cloudflared
|
||||
general_definition: |-
|
||||
the software powering Cloudflare Tunnel. It runs on origin servers to connect applications or private networks to Cloudflare.
|
||||
- term: cloudflared
|
||||
general_definition: |-
|
||||
the software powering Cloudflare Tunnel. It runs on origin servers to connect applications or private networks to Cloudflare.
|
||||
|
||||
- term: cloudflared replica
|
||||
general_definition: |-
|
||||
an additional instance of `cloudflared` that points to the same Cloudflare Tunnel. It ensures that your network remains online in case a single host running `cloudflared` goes down.
|
||||
- term: cloudflared replica
|
||||
general_definition: |-
|
||||
an additional instance of `cloudflared` that points to the same Cloudflare Tunnel. It ensures that your network remains online in case a single host running `cloudflared` goes down.
|
||||
|
||||
- term: Cloudflare Access
|
||||
general_definition: |-
|
||||
Cloudflare Access replaces corporate VPNs with Cloudflare’s network. It verifies attributes such as identity and device posture to grant users secure access to internal tools.
|
||||
- term: Cloudflare Access
|
||||
general_definition: |-
|
||||
Cloudflare Access replaces corporate VPNs with Cloudflare’s network. It verifies attributes such as identity and device posture to grant users secure access to internal tools.
|
||||
|
||||
- term: Cloudflare Browser Isolation
|
||||
general_definition: |-
|
||||
Cloudflare Browser Isolation seamlessly executes active webpage content in a secure isolated browser to protect users from zero-day attacks, malware, and phishing.
|
||||
- term: Cloudflare Browser Isolation
|
||||
general_definition: |-
|
||||
Cloudflare Browser Isolation seamlessly executes active webpage content in a secure isolated browser to protect users from zero-day attacks, malware, and phishing.
|
||||
|
||||
- term: Cloudflare CASB
|
||||
general_definition: |-
|
||||
Cloudflare CASB provides comprehensive visibility and control over SaaS apps to prevent data leaks and compliance violations. It helps detect insider threats, shadow IT, risky data sharing, and bad actors.
|
||||
- term: Cloudflare CASB
|
||||
general_definition: |-
|
||||
Cloudflare CASB provides comprehensive visibility and control over SaaS apps to prevent data leaks and compliance violations. It helps detect insider threats, shadow IT, risky data sharing, and bad actors.
|
||||
|
||||
- term: Cloudflare Data Loss Prevention (DLP)
|
||||
general_definition: |-
|
||||
Cloudflare Data Loss Prevention (DLP) allows you to scan your web traffic and SaaS applications for the presence of sensitive data such as social security numbers, financial information, secret keys, and source code.
|
||||
- term: Cloudflare Data Loss Prevention (DLP)
|
||||
general_definition: |-
|
||||
Cloudflare Data Loss Prevention (DLP) allows you to scan your web traffic and SaaS applications for the presence of sensitive data such as social security numbers, financial information, secret keys, and source code.
|
||||
|
||||
- term: Cloudflare DEX
|
||||
general_definition: |-
|
||||
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust organization.
|
||||
- term: Cloudflare DEX
|
||||
general_definition: |-
|
||||
Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust organization.
|
||||
|
||||
- term: Cloudflare Gateway
|
||||
general_definition: |-
|
||||
Cloudflare Gateway is a modern next-generation firewall between your user, device, or network and the public Internet. It includes DNS filtering to inspect and apply policies to all Internet-bound DNS queries.
|
||||
- term: Cloudflare Gateway
|
||||
general_definition: |-
|
||||
Cloudflare Gateway is a modern next-generation firewall between your user, device, or network and the public Internet. It includes DNS filtering to inspect and apply policies to all Internet-bound DNS queries.
|
||||
|
||||
- term: Cloudflare One Agent
|
||||
general_definition: |-
|
||||
the name of the Cloudflare WARP client app on iOS and Android devices.
|
||||
- term: Cloudflare One Agent
|
||||
general_definition: |-
|
||||
the name of the Cloudflare WARP client app on iOS and Android devices.
|
||||
|
||||
- term: Cloudflare Tunnel
|
||||
general_definition: |-
|
||||
Cloudflare Tunnel uses software agents (`cloudflared` or WARP Connector) to establish a secure connection between a private network and Cloudflare.
|
||||
- term: Cloudflare Tunnel
|
||||
general_definition: |-
|
||||
Cloudflare Tunnel uses software agents (`cloudflared` or WARP Connector) to establish a secure connection between a private network and Cloudflare.
|
||||
|
||||
- term: Cloudflare Zero Trust
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust provides the power of Cloudflare’s global network to your internal teams and infrastructure. It empowers users with secure, fast, and seamless access to any device on the Internet.
|
||||
- term: Cloudflare Zero Trust
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust provides the power of Cloudflare’s global network to your internal teams and infrastructure. It empowers users with secure, fast, and seamless access to any device on the Internet.
|
||||
|
||||
- term: daemon
|
||||
general_definition: |-
|
||||
a program that performs tasks without active management or maintenance.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
- term: daemon
|
||||
general_definition: |-
|
||||
a program that performs tasks without active management or maintenance.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
|
||||
- term: device posture
|
||||
general_definition: |-
|
||||
a way to evaluate the security of a user's device, for example by verifying its serial number or checking if it has the latest software updates.
|
||||
- term: device posture
|
||||
general_definition: |-
|
||||
a way to evaluate the security of a user's device, for example by verifying its serial number or checking if it has the latest software updates.
|
||||
|
||||
- term: device profile
|
||||
general_definition: |-
|
||||
a collection of WARP client settings applied to a specific set of devices in your organization.
|
||||
- term: device profile
|
||||
general_definition: |-
|
||||
a collection of WARP client settings applied to a specific set of devices in your organization.
|
||||
|
||||
- term: DNS filtering
|
||||
general_definition: |-
|
||||
DNS filtering uses the Domain Name System to block malicious websites and filter out harmful content, enhancing security and access control.
|
||||
associated_products:
|
||||
- DNS
|
||||
- term: DNS filtering
|
||||
general_definition: |-
|
||||
DNS filtering uses the Domain Name System to block malicious websites and filter out harmful content, enhancing security and access control.
|
||||
associated_products:
|
||||
- DNS
|
||||
|
||||
- term: DoH subdomain
|
||||
general_definition: |-
|
||||
a unique DoH subdomain for each DNS location in Cloudflare Zero Trust used in WARP client settings.
|
||||
- term: DoH subdomain
|
||||
general_definition: |-
|
||||
a unique DoH subdomain for each DNS location in Cloudflare Zero Trust used in WARP client settings.
|
||||
|
||||
- term: DNS location
|
||||
general_definition: |-
|
||||
DNS locations are a collection of DNS endpoints which can be mapped to physical entities such as offices, homes, or data centers.
|
||||
associated_products:
|
||||
- DNS
|
||||
- term: DNS location
|
||||
general_definition: |-
|
||||
DNS locations are a collection of DNS endpoints which can be mapped to physical entities such as offices, homes, or data centers.
|
||||
associated_products:
|
||||
- DNS
|
||||
|
||||
- term: identity provider
|
||||
general_definition: |-
|
||||
an identity provider (IdP) stores and manages users' digital identities, enabling single sign-on and authentication for multiple applications.
|
||||
- term: identity provider
|
||||
general_definition: |-
|
||||
an identity provider (IdP) stores and manages users' digital identities, enabling single sign-on and authentication for multiple applications.
|
||||
|
||||
- term: JSON web token
|
||||
general_definition: |-
|
||||
a compact way to securely transmit information between parties as a JSON object, often used for authentication.
|
||||
- term: JSON web token
|
||||
general_definition: |-
|
||||
a compact way to securely transmit information between parties as a JSON object, often used for authentication.
|
||||
|
||||
- term: locally-managed tunnel
|
||||
general_definition: |-
|
||||
a Cloudflare Tunnel that was created by running `cloudflared tunnel create <NAME>` on the command line. Tunnel configuration is stored in your local `cloudflared` directory.
|
||||
- term: locally-managed tunnel
|
||||
general_definition: |-
|
||||
a Cloudflare Tunnel that was created by running `cloudflared tunnel create <NAME>` on the command line. Tunnel configuration is stored in your local `cloudflared` directory.
|
||||
|
||||
- term: managed network
|
||||
general_definition: |-
|
||||
a network location, such as an office, that is associated with a specific WARP client device profile.
|
||||
- term: managed network
|
||||
general_definition: |-
|
||||
a network location, such as an office, that is associated with a specific WARP client device profile.
|
||||
|
||||
- term: MDM file
|
||||
general_definition: |-
|
||||
a Mobile Device Management (MDM) file is a configuration file that allows organizations to manage the software, settings, and certificates installed on their devices.
|
||||
- term: MDM file
|
||||
general_definition: |-
|
||||
a Mobile Device Management (MDM) file is a configuration file that allows organizations to manage the software, settings, and certificates installed on their devices.
|
||||
|
||||
- term: MFA
|
||||
general_definition: |-
|
||||
Multi-factor authentication (MFA) checks multiple aspects of a user's identity, not only their username and password, before allowing them access to an application.
|
||||
- term: MFA
|
||||
general_definition: |-
|
||||
Multi-factor authentication (MFA) checks multiple aspects of a user's identity, not only their username and password, before allowing them access to an application.
|
||||
|
||||
- term: OAuth
|
||||
general_definition: |-
|
||||
a protocol for authorizing users, allowing them to perform actions and view data on different platforms without sharing credentials.
|
||||
- term: OAuth
|
||||
general_definition: |-
|
||||
a protocol for authorizing users, allowing them to perform actions and view data on different platforms without sharing credentials.
|
||||
|
||||
- term: OIDC
|
||||
general_definition: |-
|
||||
OpenID Connect (OIDC) is an identity authentication protocol built on top of OAuth 2.0. It is used verifying user identity and obtaining basic profile information.
|
||||
- term: OIDC
|
||||
general_definition: |-
|
||||
OpenID Connect (OIDC) is an identity authentication protocol built on top of OAuth 2.0. It is used verifying user identity and obtaining basic profile information.
|
||||
|
||||
- term: PAC file
|
||||
general_definition: |-
|
||||
a file containing a JavaScript function which can instruct a browser to forward traffic to a proxy server instead of directly to the destination server.
|
||||
- term: PAC file
|
||||
general_definition: |-
|
||||
a file containing a JavaScript function which can instruct a browser to forward traffic to a proxy server instead of directly to the destination server.
|
||||
|
||||
- term: policy
|
||||
general_definition: |-
|
||||
a set of rules that regulate network activity, such as login access and website reachability.
|
||||
- term: policy
|
||||
general_definition: |-
|
||||
a set of rules that regulate network activity, such as login access and website reachability.
|
||||
|
||||
- term: remotely-managed tunnel
|
||||
general_definition: |-
|
||||
a Cloudflare Tunnel that was created in Zero Trust under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the API.
|
||||
- term: remotely-managed tunnel
|
||||
general_definition: |-
|
||||
a Cloudflare Tunnel that was created in Zero Trust under **Networks** > **Tunnels**. Tunnel configuration is stored in Cloudflare, which allows you to manage the tunnel from the dashboard or using the API.
|
||||
|
||||
- term: RDP
|
||||
general_definition: |-
|
||||
Remote Desktop Protocol (RDP) allows remote desktop connections to a computer, often used on Windows and Mac operating systems.
|
||||
- term: RDP
|
||||
general_definition: |-
|
||||
Remote Desktop Protocol (RDP) allows remote desktop connections to a computer, often used on Windows and Mac operating systems.
|
||||
|
||||
- term: SafeSearch
|
||||
general_definition: |-
|
||||
SafeSearch is a feature of search engines that filters explicit or offensive content from search results.
|
||||
- term: SafeSearch
|
||||
general_definition: |-
|
||||
SafeSearch is a feature of search engines that filters explicit or offensive content from search results.
|
||||
|
||||
- term: SAML
|
||||
general_definition: |-
|
||||
Security Assertion Markup Language (SAML) enables single sign-on and authentication for multiple applications.
|
||||
associated_products:
|
||||
- Area 1
|
||||
- term: SAML
|
||||
general_definition: |-
|
||||
Security Assertion Markup Language (SAML) enables single sign-on and authentication for multiple applications.
|
||||
associated_products:
|
||||
- Area 1
|
||||
|
||||
- term: SASE
|
||||
general_definition: |-
|
||||
Secure Access Service Edge (SASE) is a cloud-based security model bundling networking and security functions.
|
||||
- term: SASE
|
||||
general_definition: |-
|
||||
Secure Access Service Edge (SASE) is a cloud-based security model bundling networking and security functions.
|
||||
|
||||
- term: SCIM
|
||||
general_definition: |-
|
||||
System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers (such as Okta or Microsoft Entra ID) to synchronize user identity information with cloud applications and services.
|
||||
- term: SCIM
|
||||
general_definition: |-
|
||||
System for Cross-domain Identity Management (SCIM) is an open standard protocol that allows identity providers (such as Okta or Microsoft Entra ID) to synchronize user identity information with cloud applications and services.
|
||||
|
||||
- term: seat
|
||||
general_definition: |-
|
||||
a unique user authenticating to an Access application or enrolling in WARP,
|
||||
- term: seat
|
||||
general_definition: |-
|
||||
a unique user authenticating to an Access application or enrolling in WARP,
|
||||
|
||||
- term: service provider (SP)
|
||||
general_definition: |-
|
||||
a service provider (SP) provides federated access to an application for a user from an identity provider (IdP).
|
||||
- term: service provider (SP)
|
||||
general_definition: |-
|
||||
a service provider (SP) provides federated access to an application for a user from an identity provider (IdP).
|
||||
|
||||
- term: service token
|
||||
general_definition: |-
|
||||
authentication credentials generated by Cloudflare Access which enable automated systems to access protected applications.
|
||||
- term: service token
|
||||
general_definition: |-
|
||||
authentication credentials generated by Cloudflare Access which enable automated systems to access protected applications.
|
||||
|
||||
- term: session
|
||||
general_definition: |-
|
||||
an event generated when a user logs in to an Access application.
|
||||
- term: session
|
||||
general_definition: |-
|
||||
an event generated when a user logs in to an Access application.
|
||||
|
||||
- term: shadow IT
|
||||
general_definition: |-
|
||||
shadow IT is the unsanctioned use of software, hardware, or other systems and services within an organization, often without the knowledge of that organization's information technology (IT) department.
|
||||
- term: shadow IT
|
||||
general_definition: |-
|
||||
shadow IT is the unsanctioned use of software, hardware, or other systems and services within an organization, often without the knowledge of that organization's information technology (IT) department.
|
||||
|
||||
For more information, refer to the [Cloudflare Learning Center](https://www.cloudflare.com/learning/access-management/what-is-shadow-it/).
|
||||
For more information, refer to the [Cloudflare Learning Center](https://www.cloudflare.com/learning/access-management/what-is-shadow-it/).
|
||||
|
||||
- term: SMB
|
||||
general_definition: |-
|
||||
Secure Messaging Block (SMB) is a network file sharing protocol used for accessing files and services on a network.
|
||||
- term: SMB
|
||||
general_definition: |-
|
||||
Secure Messaging Block (SMB) is a network file sharing protocol used for accessing files and services on a network.
|
||||
|
||||
- term: SSH
|
||||
general_definition: |-
|
||||
Secure Shell (SSH) protocol allows users to connect to infrastructure remotely and execute commands.
|
||||
- term: SSH
|
||||
general_definition: |-
|
||||
Secure Shell (SSH) protocol allows users to connect to infrastructure remotely and execute commands.
|
||||
|
||||
- term: SSO
|
||||
general_definition: |-
|
||||
Single Sign-On (SSO) is a technology that combines multiple application logins into one, requiring users to enter credentials only once.
|
||||
- term: SSO
|
||||
general_definition: |-
|
||||
Single Sign-On (SSO) is a technology that combines multiple application logins into one, requiring users to enter credentials only once.
|
||||
|
||||
- term: team domain
|
||||
general_definition: |-
|
||||
a unique subdomain assigned to your Cloudflare account (for example, `<your-team-name>.cloudflareaccess.com`), where users will find the apps you have secured behind Cloudflare Zero Trust.
|
||||
- term: team domain
|
||||
general_definition: |-
|
||||
a unique subdomain assigned to your Cloudflare account (for example, `<your-team-name>.cloudflareaccess.com`), where users will find the apps you have secured behind Cloudflare Zero Trust.
|
||||
|
||||
- term: team name
|
||||
general_definition: |-
|
||||
the customizable portion of your team domain, allowing you to personalize your Cloudflare Zero Trust configuration. You can view your team name in Zero Trust under **Settings** > **Custom Pages**.
|
||||
- term: team name
|
||||
general_definition: |-
|
||||
the customizable portion of your team domain, allowing you to personalize your Cloudflare Zero Trust configuration. You can view your team name in Zero Trust under **Settings** > **Custom Pages**.
|
||||
|
||||
| team domain | team name |
|
||||
| --------------------------------------- | ---------------- |
|
||||
| `<your-team-name>.cloudflareaccess.com` | `your-team-name` |
|
||||
| team domain | team name |
|
||||
| --------------------------------------- | ---------------- |
|
||||
| `<your-team-name>.cloudflareaccess.com` | `your-team-name` |
|
||||
|
||||
To learn about the consequences of changing your team name, refer to the [FAQ](/cloudflare-one/faq/teams-getting-started-faq/#whats-a-team-domain/team-name).
|
||||
To learn about the consequences of changing your team name, refer to the [FAQ](/cloudflare-one/faq/teams-getting-started-faq/#whats-a-team-domain/team-name).
|
||||
|
||||
- term: Terraform
|
||||
general_definition: |-
|
||||
an infrastructure as code software tool that allows you to deploy services from different providers using a standardized configuration syntax.
|
||||
associated_products:
|
||||
- Terraform
|
||||
- term: Terraform
|
||||
general_definition: |-
|
||||
an infrastructure as code software tool that allows you to deploy services from different providers using a standardized configuration syntax.
|
||||
associated_products:
|
||||
- Terraform
|
||||
|
||||
- term: tunnel
|
||||
general_definition: |-
|
||||
a secure pathway for network traffic to flow between a device and Cloudflare's global network.
|
||||
- term: tunnel
|
||||
general_definition: |-
|
||||
a secure pathway for network traffic to flow between a device and Cloudflare's global network.
|
||||
|
||||
- term: User risk score
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust user risk score ranks the likelihood of a user to introduce risk to your organization's systems and data based on the detection of security risk behaviors. Risk scores add user and entity behavior analytics (UEBA) to the Zero Trust platform.
|
||||
- term: User risk score
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust user risk score ranks the likelihood of a user to introduce risk to your organization's systems and data based on the detection of security risk behaviors. Risk scores add user and entity behavior analytics (UEBA) to the Zero Trust platform.
|
||||
|
||||
- term: User risk score level
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust assigns a risk score of Low, Medium or High based on detections of users' activities, posture, and settings. A user's risk score is equal to the highest-level risk behavior they trigger.
|
||||
- term: User risk score level
|
||||
general_definition: |-
|
||||
Cloudflare Zero Trust assigns a risk score of Low, Medium or High based on detections of users' activities, posture, and settings. A user's risk score is equal to the highest-level risk behavior they trigger.
|
||||
|
||||
- term: Virtual network
|
||||
general_definition: |-
|
||||
a software abstraction that allows you to logically segregate resources on a private network. Virtual networks are especially useful for exposing resources which have overlapping IP routes.
|
||||
- term: Virtual network
|
||||
general_definition: |-
|
||||
a software abstraction that allows you to logically segregate resources on a private network. Virtual networks are especially useful for exposing resources which have overlapping IP routes.
|
||||
|
||||
- term: Virtual Private Network (VPN)
|
||||
general_definition: |-
|
||||
a tool that allows users to send and receive data across shared or public networks as if their devices were directly connected to the private network. For example, employees working from home can use a VPN to access files on the corporate network.
|
||||
- term: Virtual Private Network (VPN)
|
||||
general_definition: |-
|
||||
a tool that allows users to send and receive data across shared or public networks as if their devices were directly connected to the private network. For example, employees working from home can use a VPN to access files on the corporate network.
|
||||
|
||||
- term: WARP client
|
||||
general_definition: |-
|
||||
an application that connects corporate devices to Cloudflare for private network access, advanced web filtering, and other security functions.
|
||||
- term: WARP client
|
||||
general_definition: |-
|
||||
an application that connects corporate devices to Cloudflare for private network access, advanced web filtering, and other security functions.
|
||||
|
||||
- term: WARP Connector
|
||||
general_definition: |-
|
||||
an extension of the WARP client used to establish site-to-site, bidirectional, and mesh networking connectivity. WARP Connector software installs on a Linux server within a private network, which then becomes a gateway for other local networks that need to on-ramp traffic to Cloudflare.
|
||||
- term: WARP Connector
|
||||
general_definition: |-
|
||||
an extension of the WARP client used to establish site-to-site, bidirectional, and mesh networking connectivity. WARP Connector software installs on a Linux server within a private network, which then becomes a gateway for other local networks that need to on-ramp traffic to Cloudflare.
|
||||
|
||||
- term: Zero Trust Security
|
||||
general_definition: |-
|
||||
Zero Trust Security is an IT security model that requires strict identity verification for every person and device accessing resources on a network.
|
||||
- term: Zero Trust Security
|
||||
general_definition: |-
|
||||
Zero Trust Security is an IT security model that requires strict identity verification for every person and device accessing resources on a network.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
productName: DDoS Protection
|
||||
entries:
|
||||
- term: IP spoofing
|
||||
general_definition: |-
|
||||
IP spoofing is the creation of Internet Protocol (IP) packets which have a modified source address to hide the identity of the sender, impersonate another computer system, or both.
|
||||
- term: IP spoofing
|
||||
general_definition: |-
|
||||
IP spoofing is the creation of Internet Protocol (IP) packets which have a modified source address to hide the identity of the sender, impersonate another computer system, or both.
|
||||
|
|
|
|||
|
|
@ -1,81 +1,81 @@
|
|||
---
|
||||
productName: DNS
|
||||
entries:
|
||||
- term: active zone
|
||||
general_definition: |-
|
||||
a DNS zone that is active on Cloudflare requires changing its nameservers to Cloudflare's for management.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- term: active zone
|
||||
general_definition: |-
|
||||
a DNS zone that is active on Cloudflare requires changing its nameservers to Cloudflare's for management.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
|
||||
- term: apex domain
|
||||
general_definition: |-
|
||||
apex domain is used to refer to a domain that does not contain a subdomain part, such as `example.com` (without `www.`). It is also known as "root domain" or "naked domain".
|
||||
- term: apex domain
|
||||
general_definition: |-
|
||||
apex domain is used to refer to a domain that does not contain a subdomain part, such as `example.com` (without `www.`). It is also known as "root domain" or "naked domain".
|
||||
|
||||
- term: DNS over HTTPS
|
||||
general_definition: |-
|
||||
DNS over HTTPS (DoH) is a standard for encrypting DNS traffic via the HTTPS protocol, preventing tracking and spoofing of DNS queries.
|
||||
associated_products:
|
||||
- 1.1.1.1
|
||||
- Cloudflare One
|
||||
- term: DNS over HTTPS
|
||||
general_definition: |-
|
||||
DNS over HTTPS (DoH) is a standard for encrypting DNS traffic via the HTTPS protocol, preventing tracking and spoofing of DNS queries.
|
||||
associated_products:
|
||||
- 1.1.1.1
|
||||
- Cloudflare One
|
||||
|
||||
- term: DNS over TLS
|
||||
general_definition: |-
|
||||
DNS over TLS (DoT) is a standard for encrypting DNS traffic using its own port (`853`) and TLS encryption.
|
||||
associated_products:
|
||||
- 1.1.1.1
|
||||
- Cloudflare One
|
||||
- term: DNS over TLS
|
||||
general_definition: |-
|
||||
DNS over TLS (DoT) is a standard for encrypting DNS traffic using its own port (`853`) and TLS encryption.
|
||||
associated_products:
|
||||
- 1.1.1.1
|
||||
- Cloudflare One
|
||||
|
||||
- term: DNS record
|
||||
general_definition: |-
|
||||
DNS records are instructions that live in authoritative DNS servers and provide information about a domain including what IP address is associated with that domain and how to handle requests for that domain.
|
||||
- term: DNS record
|
||||
general_definition: |-
|
||||
DNS records are instructions that live in authoritative DNS servers and provide information about a domain including what IP address is associated with that domain and how to handle requests for that domain.
|
||||
|
||||
- term: DNS server
|
||||
general_definition: |-
|
||||
DNS servers translate human-readable domain names into IP addresses, eliminating the need to remember complex IP addresses.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- term: DNS server
|
||||
general_definition: |-
|
||||
DNS servers translate human-readable domain names into IP addresses, eliminating the need to remember complex IP addresses.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
|
||||
- term: DNS zone
|
||||
general_definition: |-
|
||||
a portion of the DNS namespace that is managed by a specific organization or administrator.
|
||||
- term: DNS zone
|
||||
general_definition: |-
|
||||
a portion of the DNS namespace that is managed by a specific organization or administrator.
|
||||
|
||||
- term: Domain Name System (DNS)
|
||||
general_definition: |-
|
||||
the Domain Name System (DNS) is the phonebook of the Internet. DNS translates domain names to IP addresses.
|
||||
- term: Domain Name System (DNS)
|
||||
general_definition: |-
|
||||
the Domain Name System (DNS) is the phonebook of the Internet. DNS translates domain names to IP addresses.
|
||||
|
||||
- term: EDNS Client Subnet (ECS)
|
||||
general_definition: |-
|
||||
ECS is a DNS extension that enables recursive DNS resolvers to include client IP address information in their DNS queries.
|
||||
- term: EDNS Client Subnet (ECS)
|
||||
general_definition: |-
|
||||
ECS is a DNS extension that enables recursive DNS resolvers to include client IP address information in their DNS queries.
|
||||
|
||||
Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html).
|
||||
associated_products:
|
||||
- Load Balancing
|
||||
- Cloudflare One
|
||||
- 1.1.1.1 (DNS Resolver)
|
||||
Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html).
|
||||
associated_products:
|
||||
- Load Balancing
|
||||
- Cloudflare One
|
||||
- 1.1.1.1 (DNS Resolver)
|
||||
|
||||
- term: hostname
|
||||
general_definition: |-
|
||||
the name given to a server or node on a network, often the public DNS name of a server.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- DDoS Protection
|
||||
- term: hostname
|
||||
general_definition: |-
|
||||
the name given to a server or node on a network, often the public DNS name of a server.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- DDoS Protection
|
||||
|
||||
- term: nameserver
|
||||
general_definition: |-
|
||||
a nameserver is a dedicated server that translates human readable hostnames (`www.example.com`) into IP addresses.
|
||||
- term: nameserver
|
||||
general_definition: |-
|
||||
a nameserver is a dedicated server that translates human readable hostnames (`www.example.com`) into IP addresses.
|
||||
|
||||
Nameservers like root servers, TLD servers, and [authoritative nameservers](/dns/nameservers/) are fundamental components of the Domain Name System (DNS).
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
Nameservers like root servers, TLD servers, and [authoritative nameservers](/dns/nameservers/) are fundamental components of the Domain Name System (DNS).
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
|
||||
- term: partial setup
|
||||
general_definition: |-
|
||||
also known as CNAME setup, a partial setup allows you to use Cloudflare's reverse proxy without using Cloudflare for your authoritative nameservers.
|
||||
- term: partial setup
|
||||
general_definition: |-
|
||||
also known as CNAME setup, a partial setup allows you to use Cloudflare's reverse proxy without using Cloudflare for your authoritative nameservers.
|
||||
|
||||
- term: proxy status
|
||||
general_definition: |-
|
||||
the proxy status of a DNS record defines whether requests for your domain will route through Cloudflare (`proxied`) or not (`DNS-only`).
|
||||
- term: proxy status
|
||||
general_definition: |-
|
||||
the proxy status of a DNS record defines whether requests for your domain will route through Cloudflare (`proxied`) or not (`DNS-only`).
|
||||
|
||||
When a [DNS record is proxied](/dns/manage-dns-records/reference/proxied-dns-records/), requests are processed according to your configurations, and Cloudflare can optimize, cache, and protect your domain. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details.
|
||||
associated_products:
|
||||
- Fundamentals
|
||||
When a [DNS record is proxied](/dns/manage-dns-records/reference/proxied-dns-records/), requests are processed according to your configurations, and Cloudflare can optimize, cache, and protect your domain. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details.
|
||||
associated_products:
|
||||
- Fundamentals
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
productName: Durable Objects
|
||||
entries:
|
||||
- term: migration
|
||||
general_definition: |-
|
||||
a Durable Object migration is a mapping process from a class name to a runtime state.
|
||||
Initiate a Durable Object migration when you need to:
|
||||
- term: migration
|
||||
general_definition: |-
|
||||
a Durable Object migration is a mapping process from a class name to a runtime state.
|
||||
Initiate a Durable Object migration when you need to:
|
||||
|
||||
- Create a new Durable Object class.
|
||||
- Rename a Durable Object class.
|
||||
- Delete a Durable Object class.
|
||||
- Transfer an existing Durable Objects class.
|
||||
- Create a new Durable Object class.
|
||||
- Rename a Durable Object class.
|
||||
- Delete a Durable Object class.
|
||||
- Transfer an existing Durable Objects class.
|
||||
|
||||
- term: alarm
|
||||
general_definition: |-
|
||||
a Durable Object alarm is a mechanism that allows you to schedule the Durable Object to be woken up at a time in the future.
|
||||
- term: alarm
|
||||
general_definition: |-
|
||||
a Durable Object alarm is a mechanism that allows you to schedule the Durable Object to be woken up at a time in the future.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
---
|
||||
productName: Area 1
|
||||
entries:
|
||||
- term: attribute
|
||||
general_definition: |-
|
||||
traffic that flows through Area 1 can receive one or more attributes, which indicate that a specific condition has been met.
|
||||
- term: attribute
|
||||
general_definition: |-
|
||||
traffic that flows through Area 1 can receive one or more attributes, which indicate that a specific condition has been met.
|
||||
|
||||
- term: disposition
|
||||
general_definition: |-
|
||||
represents Area 1's evaluation of a specific message. For example, after evaluating an email it may get a disposition of `malicious`. Email messages with this disposition exhibit characteristics typical of malicious emails.
|
||||
- term: disposition
|
||||
general_definition: |-
|
||||
represents Area 1's evaluation of a specific message. For example, after evaluating an email it may get a disposition of `malicious`. Email messages with this disposition exhibit characteristics typical of malicious emails.
|
||||
|
||||
- term: phishing
|
||||
general_definition: |-
|
||||
the practice of trying to acquire sensitive data through fraudulent emails or other means. Usually, the perpetrators try to pass for a legitimate company when asking for sensitive data.
|
||||
- term: phishing
|
||||
general_definition: |-
|
||||
the practice of trying to acquire sensitive data through fraudulent emails or other means. Usually, the perpetrators try to pass for a legitimate company when asking for sensitive data.
|
||||
|
||||
- term: SMTP
|
||||
general_definition: |-
|
||||
stands for Simple Mail Transfer Protocol. It is an Internet standard based on TCP/IP to send and receive email.
|
||||
- term: SMTP
|
||||
general_definition: |-
|
||||
stands for Simple Mail Transfer Protocol. It is an Internet standard based on TCP/IP to send and receive email.
|
||||
|
|
|
|||
|
|
@ -1,186 +1,186 @@
|
|||
---
|
||||
productName: Fundamentals
|
||||
entries:
|
||||
- term: account
|
||||
general_definition: |-
|
||||
accounts group one or more members together with specific roles or permissions. Accounts can be associated with any number of domains.
|
||||
- term: account
|
||||
general_definition: |-
|
||||
accounts group one or more members together with specific roles or permissions. Accounts can be associated with any number of domains.
|
||||
|
||||
- term: API key
|
||||
general_definition: |-
|
||||
an API key is unique to each Cloudflare user and used to confirm identity when using the [Cloudflare API](/api/).
|
||||
- term: API key
|
||||
general_definition: |-
|
||||
an API key is unique to each Cloudflare user and used to confirm identity when using the [Cloudflare API](/api/).
|
||||
|
||||
- term: API token
|
||||
general_definition: |-
|
||||
API tokens authorize access to specific Cloudflare dashboard pages, accounts, and zones. API tokens are associated to the user that created them.
|
||||
- term: API token
|
||||
general_definition: |-
|
||||
API tokens authorize access to specific Cloudflare dashboard pages, accounts, and zones. API tokens are associated to the user that created them.
|
||||
|
||||
- term: backup codes
|
||||
general_definition: |-
|
||||
backup codes allow restoration of Cloudflare account access outside the normal [two-factor authentication process](/fundamentals/setup/account/account-security/2fa/). A backup code becomes invalid after use.
|
||||
- term: backup codes
|
||||
general_definition: |-
|
||||
backup codes allow restoration of Cloudflare account access outside the normal [two-factor authentication process](/fundamentals/setup/account/account-security/2fa/). A backup code becomes invalid after use.
|
||||
|
||||
- term: CIDR
|
||||
general_definition: |-
|
||||
CIDR stands for Classless Inter-Domain Routing. CIDR often refers to CIDR notation, which is an IP address represented as a series of four 8-bit octets, separated by dots (e.g., 192.168.1.1). Additionally, CIDR notation includes a suffix that indicates the number of bits used for the network portion of the address. The format is typically written as "/X," where X is the number of bits in the network portion.
|
||||
- term: CIDR
|
||||
general_definition: |-
|
||||
CIDR stands for Classless Inter-Domain Routing. CIDR often refers to CIDR notation, which is an IP address represented as a series of four 8-bit octets, separated by dots (e.g., 192.168.1.1). Additionally, CIDR notation includes a suffix that indicates the number of bits used for the network portion of the address. The format is typically written as "/X," where X is the number of bits in the network portion.
|
||||
|
||||
- term: cloud
|
||||
general_definition: |-
|
||||
a network of remote servers used to store and maintain data.
|
||||
- term: cloud
|
||||
general_definition: |-
|
||||
a network of remote servers used to store and maintain data.
|
||||
|
||||
- term: content delivery network (CDN)
|
||||
general_definition: |-
|
||||
a geographically distributed group of servers which work together to provide fast delivery of Internet content.
|
||||
associated_products:
|
||||
- Cache
|
||||
- DDoS Protection
|
||||
- term: content delivery network (CDN)
|
||||
general_definition: |-
|
||||
a geographically distributed group of servers which work together to provide fast delivery of Internet content.
|
||||
associated_products:
|
||||
- Cache
|
||||
- DDoS Protection
|
||||
|
||||
- term: content security policy (CSP)
|
||||
general_definition: |-
|
||||
an added layer of security that helps detect and mitigate certain types of attacks such as cross-site scripting (XSS) attacks.
|
||||
- term: content security policy (CSP)
|
||||
general_definition: |-
|
||||
an added layer of security that helps detect and mitigate certain types of attacks such as cross-site scripting (XSS) attacks.
|
||||
|
||||
- term: credit
|
||||
general_definition: |-
|
||||
an amount applied to a specific Cloudflare account as credit for recurring subscriptions or plan payments. The Cloudflare billing system automatically applies credits in the next billing cycle.
|
||||
- term: credit
|
||||
general_definition: |-
|
||||
an amount applied to a specific Cloudflare account as credit for recurring subscriptions or plan payments. The Cloudflare billing system automatically applies credits in the next billing cycle.
|
||||
|
||||
- term: data center
|
||||
general_definition: |-
|
||||
a physical location where servers run and other IT operations are hosted.
|
||||
- term: data center
|
||||
general_definition: |-
|
||||
a physical location where servers run and other IT operations are hosted.
|
||||
|
||||
- term: demo application
|
||||
general_definition: |-
|
||||
a demo application is a functional application in GitHub that you can clone and deploy on your own.
|
||||
- term: demo application
|
||||
general_definition: |-
|
||||
a demo application is a functional application in GitHub that you can clone and deploy on your own.
|
||||
|
||||
- term: denial-of-service (DoS) attack
|
||||
general_definition: |-
|
||||
a DoS attack is a type of cyber attack in which an attacker aims to render a computer or other device unavailable to its intended users by interrupting the device's normal functioning.
|
||||
- term: denial-of-service (DoS) attack
|
||||
general_definition: |-
|
||||
a DoS attack is a type of cyber attack in which an attacker aims to render a computer or other device unavailable to its intended users by interrupting the device's normal functioning.
|
||||
|
||||
- term: distributed denial-of-service (DDoS) attack
|
||||
general_definition: |-
|
||||
a DDoS attack is a malicious attempt to disrupt normal traffic of a targeted server, service, or network by overwhelming the target or its surrounding infrastructure with a flood of Internet traffic.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
- Magic Network Monitoring
|
||||
- term: distributed denial-of-service (DDoS) attack
|
||||
general_definition: |-
|
||||
a DDoS attack is a malicious attempt to disrupt normal traffic of a targeted server, service, or network by overwhelming the target or its surrounding infrastructure with a flood of Internet traffic.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
- Magic Network Monitoring
|
||||
|
||||
- term: domain
|
||||
general_definition: |-
|
||||
the domain name of your application on Cloudflare.
|
||||
- term: domain
|
||||
general_definition: |-
|
||||
the domain name of your application on Cloudflare.
|
||||
|
||||
- term: edge response status code
|
||||
general_definition: |-
|
||||
HTTP response code sent from Cloudflare to the client (end user). The Cloudflare dashboard **Analytics** app uses the edge response status code.
|
||||
- term: edge response status code
|
||||
general_definition: |-
|
||||
HTTP response code sent from Cloudflare to the client (end user). The Cloudflare dashboard **Analytics** app uses the edge response status code.
|
||||
|
||||
- term: code example
|
||||
general_definition: |-
|
||||
a code example illustrates how to use a programming element to implement specific functionality
|
||||
- term: code example
|
||||
general_definition: |-
|
||||
a code example illustrates how to use a programming element to implement specific functionality
|
||||
|
||||
- term: feature
|
||||
general_definition: |-
|
||||
a feature is a setting in the Cloudflare dashboard that corresponds to functionality within a Cloudflare product or API.
|
||||
- term: feature
|
||||
general_definition: |-
|
||||
a feature is a setting in the Cloudflare dashboard that corresponds to functionality within a Cloudflare product or API.
|
||||
|
||||
- term: HTTP request
|
||||
general_definition: |-
|
||||
an HTTP request is the way Internet communications platforms such as web browsers ask for the information they need to load a website.
|
||||
associated_products:
|
||||
- Logs
|
||||
- term: HTTP request
|
||||
general_definition: |-
|
||||
an HTTP request is the way Internet communications platforms such as web browsers ask for the information they need to load a website.
|
||||
associated_products:
|
||||
- Logs
|
||||
|
||||
- term: IP address
|
||||
general_definition: |-
|
||||
IP stands for Internet Protocol, which is the set of rules that makes it possible for devices to communicate over the Internet. With billions of people accessing the Internet every day, unique identifiers are necessary to keep track of who is doing what. The Internet Protocol solves this by assigning IP numbers to every device accessing the Internet. Every assigned number is an IP address.
|
||||
- term: IP address
|
||||
general_definition: |-
|
||||
IP stands for Internet Protocol, which is the set of rules that makes it possible for devices to communicate over the Internet. With billions of people accessing the Internet every day, unique identifiers are necessary to keep track of who is doing what. The Internet Protocol solves this by assigning IP numbers to every device accessing the Internet. Every assigned number is an IP address.
|
||||
|
||||
- term: Internet
|
||||
general_definition: |-
|
||||
the Internet is a global system of computer networks that provides a wide range of information and communication facilities.
|
||||
- term: Internet
|
||||
general_definition: |-
|
||||
the Internet is a global system of computer networks that provides a wide range of information and communication facilities.
|
||||
|
||||
- term: member or user
|
||||
general_definition: |-
|
||||
a member or user is an email account in Cloudflare that you can grant access to your organization account. Members belonging to multiple accounts can select which account to manage via the Cloudflare dashboard.
|
||||
- term: member or user
|
||||
general_definition: |-
|
||||
a member or user is an email account in Cloudflare that you can grant access to your organization account. Members belonging to multiple accounts can select which account to manage via the Cloudflare dashboard.
|
||||
|
||||
- term: origin request
|
||||
general_definition: |-
|
||||
an origin request is a request served from the origin server.
|
||||
- term: origin request
|
||||
general_definition: |-
|
||||
an origin request is a request served from the origin server.
|
||||
|
||||
- term: origin response status code
|
||||
general_definition: |-
|
||||
an origin response status code is an HTTP response code sent from the origin server to Cloudflare.
|
||||
- term: origin response status code
|
||||
general_definition: |-
|
||||
an origin response status code is an HTTP response code sent from the origin server to Cloudflare.
|
||||
|
||||
- term: plan
|
||||
general_definition: |-
|
||||
plans distinguish the breadth of Cloudflare features accessible to a specific domain. Plan options include [Free, Pro, Business, or Enterprise](https://www.cloudflare.com/plans/).
|
||||
- term: plan
|
||||
general_definition: |-
|
||||
plans distinguish the breadth of Cloudflare features accessible to a specific domain. Plan options include [Free, Pro, Business, or Enterprise](https://www.cloudflare.com/plans/).
|
||||
|
||||
- term: protocol
|
||||
general_definition: |-
|
||||
a protocol is a set of rules governing the exchange or transmission of data between devices.
|
||||
- term: protocol
|
||||
general_definition: |-
|
||||
a protocol is a set of rules governing the exchange or transmission of data between devices.
|
||||
|
||||
- term: redirect
|
||||
general_definition: |-
|
||||
URL redirects navigate the user from a source URL to a target URL using a given HTTP status code. URL redirection is also known as URL forwarding.
|
||||
- term: redirect
|
||||
general_definition: |-
|
||||
URL redirects navigate the user from a source URL to a target URL using a given HTTP status code. URL redirection is also known as URL forwarding.
|
||||
|
||||
- term: reference architecture
|
||||
general_definition: |-
|
||||
A reference architecture provides a high-level view of how all or part of the Cloudflare platform is built and how Cloudflare products would fit into a customer's existing infrastructure.
|
||||
- term: reference architecture
|
||||
general_definition: |-
|
||||
A reference architecture provides a high-level view of how all or part of the Cloudflare platform is built and how Cloudflare products would fit into a customer's existing infrastructure.
|
||||
|
||||
- term: roles
|
||||
general_definition: |-
|
||||
authorize which Cloudflare products and features a member is allowed to access in a Cloudflare account. Learn more about [roles](/fundamentals/setup/manage-members/roles/).
|
||||
- term: roles
|
||||
general_definition: |-
|
||||
authorize which Cloudflare products and features a member is allowed to access in a Cloudflare account. Learn more about [roles](/fundamentals/setup/manage-members/roles/).
|
||||
|
||||
- term: Service Level Agreement (SLA)
|
||||
general_definition: |-
|
||||
an SLA is a contractual obligation for Cloudflare to maintain a specific level of service. Read the [Service Level Agreement (SLA) for the Cloudflare Business plan](https://www.cloudflare.com/business-sla/). Enterprise customers refer to the Enterprise SLA provided with their contract.
|
||||
- term: Service Level Agreement (SLA)
|
||||
general_definition: |-
|
||||
an SLA is a contractual obligation for Cloudflare to maintain a specific level of service. Read the [Service Level Agreement (SLA) for the Cloudflare Business plan](https://www.cloudflare.com/business-sla/). Enterprise customers refer to the Enterprise SLA provided with their contract.
|
||||
|
||||
- term: traffic
|
||||
general_definition: |-
|
||||
traffic is the data sent and received by visitors to a website. Cloudflare serves and protects this data as it passes through the Cloudflare network.
|
||||
- term: traffic
|
||||
general_definition: |-
|
||||
traffic is the data sent and received by visitors to a website. Cloudflare serves and protects this data as it passes through the Cloudflare network.
|
||||
|
||||
- term: tutorial
|
||||
general_definition: |-
|
||||
a tutorial is a practical lesson that takes you from a clear starting to ending point.
|
||||
- term: tutorial
|
||||
general_definition: |-
|
||||
a tutorial is a practical lesson that takes you from a clear starting to ending point.
|
||||
|
||||
The goal is to connect products to real-world scenarios to meet a user’s goal.
|
||||
The goal is to connect products to real-world scenarios to meet a user’s goal.
|
||||
|
||||
- term: two-factor authentication (2FA)
|
||||
general_definition: |-
|
||||
Two-factor authentication (2FA) is a security process in which a user provides two different authentication factors to verify their identity. In addition to something you know, typically your password, 2FA adds an extra layer of security to user logins by requiring users to also present something they have, such as Yubikey or a one-time login code, or something you are, such as a fingerprint.
|
||||
- term: two-factor authentication (2FA)
|
||||
general_definition: |-
|
||||
Two-factor authentication (2FA) is a security process in which a user provides two different authentication factors to verify their identity. In addition to something you know, typically your password, 2FA adds an extra layer of security to user logins by requiring users to also present something they have, such as Yubikey or a one-time login code, or something you are, such as a fingerprint.
|
||||
|
||||
It adds an extra layer of security to user logins by requiring users to present two or more separate pieces of evidence (factors) that establish their identity.
|
||||
associated_products:
|
||||
- Area 1
|
||||
It adds an extra layer of security to user logins by requiring users to present two or more separate pieces of evidence (factors) that establish their identity.
|
||||
associated_products:
|
||||
- Area 1
|
||||
|
||||
- term: website
|
||||
general_definition: |-
|
||||
a website is a collection of web pages and related content that is identified by a common domain name and published on at least one web server.
|
||||
- term: website
|
||||
general_definition: |-
|
||||
a website is a collection of web pages and related content that is identified by a common domain name and published on at least one web server.
|
||||
|
||||
- term: zone
|
||||
general_definition: |-
|
||||
a zone is a portion of DNS namespace that is managed by a specific organization or administrator.
|
||||
- term: zone
|
||||
general_definition: |-
|
||||
a zone is a portion of DNS namespace that is managed by a specific organization or administrator.
|
||||
|
||||
- term: request
|
||||
general_definition: |-
|
||||
a request is a message that is sent between a client, or web browser, to a server. Each request that has been processed through the Cloudflare network generates a record.
|
||||
associated_products:
|
||||
- Logs
|
||||
- term: request
|
||||
general_definition: |-
|
||||
a request is a message that is sent between a client, or web browser, to a server. Each request that has been processed through the Cloudflare network generates a record.
|
||||
associated_products:
|
||||
- Logs
|
||||
|
||||
- term: TCP Keep-Alive
|
||||
general_definition: |-
|
||||
a TCP keep-alive is used to maintain a connection between two endpoints by sending packets to check if the connection is still active. This helps prevent idle connections from being prematurely closed. If a response is not received after a defined period, the connection is terminated.
|
||||
- term: TCP Keep-Alive
|
||||
general_definition: |-
|
||||
a TCP keep-alive is used to maintain a connection between two endpoints by sending packets to check if the connection is still active. This helps prevent idle connections from being prematurely closed. If a response is not received after a defined period, the connection is terminated.
|
||||
|
||||
- term: TCP RST (reset)
|
||||
general_definition: |-
|
||||
a TCP Reset (RST) packet is used by a TCP sender to close a connection.
|
||||
- term: TCP RST (reset)
|
||||
general_definition: |-
|
||||
a TCP Reset (RST) packet is used by a TCP sender to close a connection.
|
||||
|
||||
- term: TCP Fast Open (TFO)
|
||||
general_definition: |-
|
||||
TCP Fast Open (TFO) is a protocol extension that can significantly improve the speed of establishing TCP connections by allowing data to be sent in the initial SYN packet, rather than requiring a separate handshake before data transmission begins.
|
||||
- term: TCP Fast Open (TFO)
|
||||
general_definition: |-
|
||||
TCP Fast Open (TFO) is a protocol extension that can significantly improve the speed of establishing TCP connections by allowing data to be sent in the initial SYN packet, rather than requiring a separate handshake before data transmission begins.
|
||||
|
||||
- term: TCP three-way handshake
|
||||
general_definition: |-
|
||||
TCP uses a three-way handshake to establish a reliable connection (SYN, SYN-ACK, ACK) over an IP based connection. SYN is short for synchronize, and ACK is short for acknowledgement.
|
||||
- term: TCP three-way handshake
|
||||
general_definition: |-
|
||||
TCP uses a three-way handshake to establish a reliable connection (SYN, SYN-ACK, ACK) over an IP based connection. SYN is short for synchronize, and ACK is short for acknowledgement.
|
||||
|
||||
- term: idle connection
|
||||
general_definition: |-
|
||||
when a TCP connection is in an idle state, it means that the connection has been established, but neither endpoint is sending any data. In the context of HTTP, an idle connection is when an established connection between a client and a server is not currently transmitting any HTTP requests or responses.
|
||||
- term: idle connection
|
||||
general_definition: |-
|
||||
when a TCP connection is in an idle state, it means that the connection has been established, but neither endpoint is sending any data. In the context of HTTP, an idle connection is when an established connection between a client and a server is not currently transmitting any HTTP requests or responses.
|
||||
|
||||
- term: proxy read timeout
|
||||
general_definition: |-
|
||||
a proxy read timeout is the maximum amount of time a proxy server waits for a response from the origin server before terminating the connection.
|
||||
- term: proxy read timeout
|
||||
general_definition: |-
|
||||
a proxy read timeout is the maximum amount of time a proxy server waits for a response from the origin server before terminating the connection.
|
||||
|
||||
- term: proxy write timeout
|
||||
general_definition: |-
|
||||
a proxy write timeout is the maximum amount of time a proxy server allows for sending data to the client before terminating the connection.
|
||||
- term: proxy write timeout
|
||||
general_definition: |-
|
||||
a proxy write timeout is the maximum amount of time a proxy server allows for sending data to the client before terminating the connection.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
productName: KV
|
||||
entries:
|
||||
- term: KV namespace
|
||||
general_definition: |-
|
||||
a KV namespace is a key-value database replicated to Cloudflare’s global network. A KV namespace must require a binding and an id.
|
||||
|
||||
- term: cacheTtl
|
||||
general_definition: |-
|
||||
cacheTtl is a parameter that defines the length of time in seconds that a KV result is cached in the global network location it is accessed from.
|
||||
- term: KV namespace
|
||||
general_definition: |-
|
||||
a KV namespace is a key-value database replicated to Cloudflare’s global network. A KV namespace must require a binding and an id.
|
||||
|
||||
- term: metadata
|
||||
general_definition: |-
|
||||
a metadata is a serializable value you append to each KV entry.
|
||||
- term: cacheTtl
|
||||
general_definition: |-
|
||||
cacheTtl is a parameter that defines the length of time in seconds that a KV result is cached in the global network location it is accessed from.
|
||||
|
||||
- term: metadata
|
||||
general_definition: |-
|
||||
a metadata is a serializable value you append to each KV entry.
|
||||
|
|
|
|||
|
|
@ -1,31 +1,31 @@
|
|||
---
|
||||
productName: Load Balancing
|
||||
entries:
|
||||
- term: endpoint
|
||||
general_definition: |-
|
||||
any service or hardware that intercepts and processes incoming public or private traffic.
|
||||
- term: endpoint
|
||||
general_definition: |-
|
||||
any service or hardware that intercepts and processes incoming public or private traffic.
|
||||
|
||||
Examples of endpoints include origins, hostnames, private or public IP addresses, virtual IP addresses (VIPs), servers, and other dedicated hardware boxes.
|
||||
Examples of endpoints include origins, hostnames, private or public IP addresses, virtual IP addresses (VIPs), servers, and other dedicated hardware boxes.
|
||||
|
||||
- term: pool
|
||||
general_definition: |-
|
||||
within Cloudflare, pools represent your endpoints and how they are organized. As such, a pool can be a group of several endpoints, or you could also have only one endpoint (an origin server, for example) per pool.
|
||||
- term: pool
|
||||
general_definition: |-
|
||||
within Cloudflare, pools represent your endpoints and how they are organized. As such, a pool can be a group of several endpoints, or you could also have only one endpoint (an origin server, for example) per pool.
|
||||
|
||||
If you are familiar with DNS terminology, think of a pool as a “record set,” except Cloudflare only returns addresses that are considered healthy. You can attach health monitors to individual pools for customized monitoring.
|
||||
If you are familiar with DNS terminology, think of a pool as a “record set,” except Cloudflare only returns addresses that are considered healthy. You can attach health monitors to individual pools for customized monitoring.
|
||||
|
||||
- term: monitor
|
||||
general_definition: |-
|
||||
a monitor issues health monitor requests at regular intervals to evaluate the health of each endpoint within a [pool](/load-balancing/pools/).
|
||||
- term: monitor
|
||||
general_definition: |-
|
||||
a monitor issues health monitor requests at regular intervals to evaluate the health of each endpoint within a [pool](/load-balancing/pools/).
|
||||
|
||||
When a pool [becomes unhealthy](/load-balancing/understand-basics/health-details/), your load balancer takes that pool out of the endpoint rotation.
|
||||
When a pool [becomes unhealthy](/load-balancing/understand-basics/health-details/), your load balancer takes that pool out of the endpoint rotation.
|
||||
|
||||
- term: health check
|
||||
general_definition: |-
|
||||
requests issued by a monitor at regular interval and — depending on the monitor settings — return a **pass** or **fail** value to make sure an endpoint is still able to receive traffic.
|
||||
- term: health check
|
||||
general_definition: |-
|
||||
requests issued by a monitor at regular interval and — depending on the monitor settings — return a **pass** or **fail** value to make sure an endpoint is still able to receive traffic.
|
||||
|
||||
Each health monitor request is trying to answer two questions:
|
||||
Each health monitor request is trying to answer two questions:
|
||||
|
||||
1. **Is the endpoint offline?**: Does the endpoint respond to the health monitor request at all? If so, does it respond quickly enough (as specified in the monitor's **Timeout** field)?
|
||||
2. **Is the endpoint working as expected?**: Does the endpoint respond with the expected HTTP response codes? Does it include specific information in the response body?
|
||||
1. **Is the endpoint offline?**: Does the endpoint respond to the health monitor request at all? If so, does it respond quickly enough (as specified in the monitor's **Timeout** field)?
|
||||
2. **Is the endpoint working as expected?**: Does the endpoint respond with the expected HTTP response codes? Does it include specific information in the response body?
|
||||
|
||||
If the answer to either of these questions is "No", then the endpoint fails the health monitor request.
|
||||
If the answer to either of these questions is "No", then the endpoint fails the health monitor request.
|
||||
|
|
|
|||
|
|
@ -1,30 +1,30 @@
|
|||
---
|
||||
productName: Logs
|
||||
entries:
|
||||
- term: log
|
||||
general_definition: |-
|
||||
a chronological record of events, actions, or transactions, typically used for tracking and troubleshooting purposes.
|
||||
- term: log
|
||||
general_definition: |-
|
||||
a chronological record of events, actions, or transactions, typically used for tracking and troubleshooting purposes.
|
||||
|
||||
- term: logging
|
||||
general_definition: |-
|
||||
the process of recording events, actions, or transactions in a log.
|
||||
- term: logging
|
||||
general_definition: |-
|
||||
the process of recording events, actions, or transactions in a log.
|
||||
|
||||
- term: timestamp
|
||||
general_definition: |-
|
||||
a data field indicating the date and time when an event occurred, often used for sequencing and analysis.
|
||||
- term: timestamp
|
||||
general_definition: |-
|
||||
a data field indicating the date and time when an event occurred, often used for sequencing and analysis.
|
||||
|
||||
- term: event
|
||||
general_definition: |-
|
||||
an occurrence or happening that is significant and worthy of being recorded in a log.
|
||||
- term: event
|
||||
general_definition: |-
|
||||
an occurrence or happening that is significant and worthy of being recorded in a log.
|
||||
|
||||
- term: log file
|
||||
general_definition: |-
|
||||
a file containing a collection of log entries, usually stored in a structured or semi-structured format.
|
||||
- term: log file
|
||||
general_definition: |-
|
||||
a file containing a collection of log entries, usually stored in a structured or semi-structured format.
|
||||
|
||||
- term: debugging
|
||||
general_definition: |-
|
||||
the process of identifying and resolving errors or issues within software applications or systems, often facilitated by analyzing log data.
|
||||
- term: debugging
|
||||
general_definition: |-
|
||||
the process of identifying and resolving errors or issues within software applications or systems, often facilitated by analyzing log data.
|
||||
|
||||
- term: deprecation
|
||||
general_definition: |-
|
||||
deprecation in software development involves officially labeling a feature as outdated. While a deprecated software feature remains within the software, users are warned and encouraged to adopt alternatives. Eventually, deprecated features may be removed. This approach ensures backward compatibility and gives programmers time to update their code.
|
||||
- term: deprecation
|
||||
general_definition: |-
|
||||
deprecation in software development involves officially labeling a feature as outdated. While a deprecated software feature remains within the software, users are warned and encouraged to adopt alternatives. Eventually, deprecated features may be removed. This approach ensures backward compatibility and gives programmers time to update their code.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
productName: Magic Firewall
|
||||
entries:
|
||||
- term: firewall-as-a-service
|
||||
general_definition: |-
|
||||
also known as cloud firewall. A security product that is hosted in the cloud.
|
||||
- term: firewall-as-a-service
|
||||
general_definition: |-
|
||||
also known as cloud firewall. A security product that is hosted in the cloud.
|
||||
|
||||
- term: bit field matching
|
||||
general_definition: |-
|
||||
matches raw bits in a packet to certain values specified in your rules.
|
||||
- term: bit field matching
|
||||
general_definition: |-
|
||||
matches raw bits in a packet to certain values specified in your rules.
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
---
|
||||
productName: Magic Network Monitoring
|
||||
entries:
|
||||
- term: flow data
|
||||
general_definition: |-
|
||||
represents records of communication between devices. There are a number of flow data protocols, such as NetFlow or sFlow.
|
||||
- term: flow data
|
||||
general_definition: |-
|
||||
represents records of communication between devices. There are a number of flow data protocols, such as NetFlow or sFlow.
|
||||
|
||||
- term: NetFlow
|
||||
general_definition: |-
|
||||
network protocol developed by Cisco to collect and monitor network traffic flow data.
|
||||
- term: NetFlow
|
||||
general_definition: |-
|
||||
network protocol developed by Cisco to collect and monitor network traffic flow data.
|
||||
|
||||
- term: sampling
|
||||
general_definition: |-
|
||||
in the context of Magic Network Monitoring, sampling is the process of taking samples of packets for a specific period to identify potential attacks.
|
||||
- term: sampling
|
||||
general_definition: |-
|
||||
in the context of Magic Network Monitoring, sampling is the process of taking samples of packets for a specific period to identify potential attacks.
|
||||
|
||||
- term: sFlow
|
||||
general_definition: |-
|
||||
an industry standard packet sampling protocol to monitor network devices.
|
||||
- term: sFlow
|
||||
general_definition: |-
|
||||
an industry standard packet sampling protocol to monitor network devices.
|
||||
|
|
|
|||
|
|
@ -1,23 +1,23 @@
|
|||
---
|
||||
productName: Magic Transit
|
||||
entries:
|
||||
- term: letter of agency
|
||||
general_definition: |-
|
||||
sometimes referred to as a Letter of Authorization. A document that authorizes Cloudflare to advertise your prefixes. This is required so transit providers can accept the routes Cloudflare advertises on your behalf.
|
||||
associated_products:
|
||||
- BYOIP
|
||||
|
||||
- term: policy-based routing
|
||||
general_definition: |-
|
||||
policy-based routing (PBR) is a technique used to make routing decisions based on policies set by your administrador.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
- term: letter of agency
|
||||
general_definition: |-
|
||||
sometimes referred to as a Letter of Authorization. A document that authorizes Cloudflare to advertise your prefixes. This is required so transit providers can accept the routes Cloudflare advertises on your behalf.
|
||||
associated_products:
|
||||
- BYOIP
|
||||
|
||||
- term: prefix
|
||||
general_definition: |-
|
||||
a number that identifies the network portion of an IP address. It tells devices if an IP address is on the same network or not. It is shown as a number after a slash (for example, `/31`) at the end of the IP address.
|
||||
|
||||
Using an analogy, the prefix is like a street address. If an IP is in the same street, it belongs to the same network of devices.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
- Magic Network Monitoring
|
||||
- term: policy-based routing
|
||||
general_definition: |-
|
||||
policy-based routing (PBR) is a technique used to make routing decisions based on policies set by your administrador.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
|
||||
- term: prefix
|
||||
general_definition: |-
|
||||
a number that identifies the network portion of an IP address. It tells devices if an IP address is on the same network or not. It is shown as a number after a slash (for example, `/31`) at the end of the IP address.
|
||||
|
||||
Using an analogy, the prefix is like a street address. If an IP is in the same street, it belongs to the same network of devices.
|
||||
associated_products:
|
||||
- Magic WAN
|
||||
- Magic Network Monitoring
|
||||
|
|
|
|||
|
|
@ -1,86 +1,86 @@
|
|||
---
|
||||
productName: Magic WAN
|
||||
entries:
|
||||
- term: anycast
|
||||
general_definition: |-
|
||||
Anycast is a network addressing and routing method in which incoming requests can be routed to a variety of different locations. Anycast typically routes incoming traffic to the nearest data center with the capacity to process the request efficiently.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: anycast
|
||||
general_definition: |-
|
||||
Anycast is a network addressing and routing method in which incoming requests can be routed to a variety of different locations. Anycast typically routes incoming traffic to the nearest data center with the capacity to process the request efficiently.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: data packet
|
||||
general_definition: |-
|
||||
a data packet is a unit of data consisting of user and control information. Information in a network is broken down into packets, that might follow different paths to their final destination.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- Magic Firewall
|
||||
- term: data packet
|
||||
general_definition: |-
|
||||
a data packet is a unit of data consisting of user and control information. Information in a network is broken down into packets, that might follow different paths to their final destination.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- Magic Firewall
|
||||
|
||||
- term: equal-cost multi-path routing
|
||||
general_definition: |-
|
||||
a technique that uses hashes calculated from packet data to determine the route chosen.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: equal-cost multi-path routing
|
||||
general_definition: |-
|
||||
a technique that uses hashes calculated from packet data to determine the route chosen.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: GRE tunnel
|
||||
general_definition: |-
|
||||
stands for generic routing encapsulation. It is a protocol wrapping one data packet within another type of data packet. This is useful for enabling protocols that are not normally supported by a network.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: GRE tunnel
|
||||
general_definition: |-
|
||||
stands for generic routing encapsulation. It is a protocol wrapping one data packet within another type of data packet. This is useful for enabling protocols that are not normally supported by a network.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: ICMP
|
||||
general_definition: |-
|
||||
Internet Control Message Protocol (ICMP) is used by network devices to send error messages and other operational information. ICMP is useful for diagnostic purposes, for example.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- DDoS Protection
|
||||
- term: ICMP
|
||||
general_definition: |-
|
||||
Internet Control Message Protocol (ICMP) is used by network devices to send error messages and other operational information. ICMP is useful for diagnostic purposes, for example.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- DDoS Protection
|
||||
|
||||
- term: Internet key exchange (IKE)
|
||||
general_definition: |-
|
||||
the protocol Cloudflare uses to create the IPsec tunnel between Magic WAN and the customer's device.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: Internet key exchange (IKE)
|
||||
general_definition: |-
|
||||
the protocol Cloudflare uses to create the IPsec tunnel between Magic WAN and the customer's device.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: IPsec tunnel
|
||||
general_definition: |-
|
||||
stands for Internet Protocol secure. It is a group of protocols for securing connections between devices, by encrypting IP packets.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: IPsec tunnel
|
||||
general_definition: |-
|
||||
stands for Internet Protocol secure. It is a group of protocols for securing connections between devices, by encrypting IP packets.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: maximum segment size (MSS)
|
||||
general_definition: |-
|
||||
MSS limits the size of packets, or small chunks of data, that travel across a network, such as the Internet.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: maximum segment size (MSS)
|
||||
general_definition: |-
|
||||
MSS limits the size of packets, or small chunks of data, that travel across a network, such as the Internet.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: on-ramp
|
||||
general_definition: |-
|
||||
refers to a way of connecting a business network to Cloudflare. Examples of on-ramps, or ways to connect to Cloudflare, are Anycast GRE tunnels, Anycast IPsec tunnels, Cloudflare Network Interconnect (CNI), Cloudflare Tunnel, and WARP.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: on-ramp
|
||||
general_definition: |-
|
||||
refers to a way of connecting a business network to Cloudflare. Examples of on-ramps, or ways to connect to Cloudflare, are Anycast GRE tunnels, Anycast IPsec tunnels, Cloudflare Network Interconnect (CNI), Cloudflare Tunnel, and WARP.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: traffic steering
|
||||
general_definition: |-
|
||||
Cloudflare evaluates your route's health and steers traffic according to priorities defined by you and / or tunnel health.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: traffic steering
|
||||
general_definition: |-
|
||||
Cloudflare evaluates your route's health and steers traffic according to priorities defined by you and / or tunnel health.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: tunnel health-check
|
||||
general_definition: |-
|
||||
a probe sent by Cloudflare to check for tunnel health. If a tunnel is not considered healthy, Cloudflare reroutes traffic to one that is considered healthy.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: tunnel health-check
|
||||
general_definition: |-
|
||||
a probe sent by Cloudflare to check for tunnel health. If a tunnel is not considered healthy, Cloudflare reroutes traffic to one that is considered healthy.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: static route
|
||||
general_definition: |-
|
||||
a fixed configuration to route traffic through Anycast tunnels from Cloudflare global network to the customer's locations.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: static route
|
||||
general_definition: |-
|
||||
a fixed configuration to route traffic through Anycast tunnels from Cloudflare global network to the customer's locations.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: subnet
|
||||
general_definition: |-
|
||||
also known as subnetwork. It refers to a network that is part of another network.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
- term: subnet
|
||||
general_definition: |-
|
||||
also known as subnetwork. It refers to a network that is part of another network.
|
||||
associated_products:
|
||||
- Magic Transit
|
||||
|
||||
- term: WAN
|
||||
general_definition: |-
|
||||
stands for Wide Area Network. It refers to a computer network that connects groups of computers over large distances. WANs are often used by businesses to connect their office networks. The objective is to make each of the local area networks (LANs) be remotely connected and accessible.
|
||||
- term: WAN
|
||||
general_definition: |-
|
||||
stands for Wide Area Network. It refers to a computer network that connects groups of computers over large distances. WANs are often used by businesses to connect their office networks. The objective is to make each of the local area networks (LANs) be remotely connected and accessible.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
productName: Queues
|
||||
entries:
|
||||
- term: queue
|
||||
general_definition: |-
|
||||
a queue is a buffer or list that automatically scales as messages are written to it, and allows a consumer Worker to pull messages from that same queue.
|
||||
- term: queue
|
||||
general_definition: |-
|
||||
a queue is a buffer or list that automatically scales as messages are written to it, and allows a consumer Worker to pull messages from that same queue.
|
||||
|
||||
- term: producer
|
||||
general_definition: |-
|
||||
a producer is the term for a client that is publishing or producing messages on to a queue.
|
||||
- term: producer
|
||||
general_definition: |-
|
||||
a producer is the term for a client that is publishing or producing messages on to a queue.
|
||||
|
||||
- term: consumer
|
||||
general_definition: |-
|
||||
a consumer is the term for a client that is subscribing to or consuming messages from a queue.
|
||||
- term: consumer
|
||||
general_definition: |-
|
||||
a consumer is the term for a client that is subscribing to or consuming messages from a queue.
|
||||
|
|
|
|||
|
|
@ -1,20 +1,20 @@
|
|||
---
|
||||
productName: Rules
|
||||
entries:
|
||||
- term: JSON web token (JWT)
|
||||
general_definition: |-
|
||||
a common authentication and authorization method used in web applications and APIs.
|
||||
associated_products:
|
||||
- API Shield
|
||||
- term: JSON web token (JWT)
|
||||
general_definition: |-
|
||||
a common authentication and authorization method used in web applications and APIs.
|
||||
associated_products:
|
||||
- API Shield
|
||||
|
||||
- term: URL normalization
|
||||
general_definition: |-
|
||||
the process of modifying the URLs of incoming requests so that they conform to a consistent formatting standard.
|
||||
- term: URL normalization
|
||||
general_definition: |-
|
||||
the process of modifying the URLs of incoming requests so that they conform to a consistent formatting standard.
|
||||
|
||||
- term: URL rewrite
|
||||
general_definition: |-
|
||||
an operation performed by a server that converts a source URL into a target URL.
|
||||
- term: URL rewrite
|
||||
general_definition: |-
|
||||
an operation performed by a server that converts a source URL into a target URL.
|
||||
|
||||
- term: Snippets subrequest
|
||||
general_definition: |-
|
||||
any request that a Snippet makes to either Internet resources using the Fetch API or requests to other Cloudflare services.
|
||||
- term: Snippets subrequest
|
||||
general_definition: |-
|
||||
any request that a Snippet makes to either Internet resources using the Fetch API or requests to other Cloudflare services.
|
||||
|
|
|
|||
|
|
@ -1,62 +1,62 @@
|
|||
---
|
||||
productName: Spectrum
|
||||
entries:
|
||||
- term: TCP (Transmission Control Protocol)
|
||||
general_definition: |-
|
||||
a connection-oriented protocol in the transport layer of the Internet Protocol Suite, providing reliable and ordered delivery of data between devices.
|
||||
- term: TCP (Transmission Control Protocol)
|
||||
general_definition: |-
|
||||
a connection-oriented protocol in the transport layer of the Internet Protocol Suite, providing reliable and ordered delivery of data between devices.
|
||||
|
||||
- term: UDP (User Datagram Protocol)
|
||||
general_definition: |-
|
||||
UDP (User Datagram Protocol) is a connectionless transport layer protocol that provides fast and lightweight data transmission between devices on a network, prioritizing speed over reliability.
|
||||
- term: UDP (User Datagram Protocol)
|
||||
general_definition: |-
|
||||
UDP (User Datagram Protocol) is a connectionless transport layer protocol that provides fast and lightweight data transmission between devices on a network, prioritizing speed over reliability.
|
||||
|
||||
- term: MQTT (Message Queuing Telemetry Transport)
|
||||
general_definition: |-
|
||||
a lightweight, publish-subscribe messaging protocol often used for communication in the Internet of Things (IoT) and other resource-constrained scenarios.
|
||||
- term: MQTT (Message Queuing Telemetry Transport)
|
||||
general_definition: |-
|
||||
a lightweight, publish-subscribe messaging protocol often used for communication in the Internet of Things (IoT) and other resource-constrained scenarios.
|
||||
|
||||
- term: proxy protocol
|
||||
general_definition: |-
|
||||
a protocol used by network proxies to convey client connection information to the destination server, facilitating proper handling of client requests.
|
||||
- term: proxy protocol
|
||||
general_definition: |-
|
||||
a protocol used by network proxies to convey client connection information to the destination server, facilitating proper handling of client requests.
|
||||
|
||||
- term: reverse proxy
|
||||
general_definition: |-
|
||||
a server that handles requests on behalf of clients, forwarding them to backend servers and managing tasks like load balancing and security.
|
||||
- term: reverse proxy
|
||||
general_definition: |-
|
||||
a server that handles requests on behalf of clients, forwarding them to backend servers and managing tasks like load balancing and security.
|
||||
|
||||
- term: layer 3
|
||||
general_definition: |-
|
||||
the network layer in the OSI model, responsible for logical addressing, routing, and forwarding of data between devices on different networks.
|
||||
- term: layer 3
|
||||
general_definition: |-
|
||||
the network layer in the OSI model, responsible for logical addressing, routing, and forwarding of data between devices on different networks.
|
||||
|
||||
- term: layer 4
|
||||
general_definition: |-
|
||||
the transport layer in the OSI model, managing end-to-end communication, error-checking, and flow control.
|
||||
- term: layer 4
|
||||
general_definition: |-
|
||||
the transport layer in the OSI model, managing end-to-end communication, error-checking, and flow control.
|
||||
|
||||
- term: OSI model (Open Systems Interconnection model)
|
||||
general_definition: |-
|
||||
a conceptual framework that standardizes the functions of a telecommunication or computing system into seven abstraction layers.
|
||||
- term: OSI model (Open Systems Interconnection model)
|
||||
general_definition: |-
|
||||
a conceptual framework that standardizes the functions of a telecommunication or computing system into seven abstraction layers.
|
||||
|
||||
- term: SYN (Synchronize)
|
||||
general_definition: |-
|
||||
the initial step in establishing a TCP connection, where a device requests a connection with another by sending a SYN packet.
|
||||
- term: SYN (Synchronize)
|
||||
general_definition: |-
|
||||
the initial step in establishing a TCP connection, where a device requests a connection with another by sending a SYN packet.
|
||||
|
||||
- term: SYN-ACK (Synchronize-Acknowledge)
|
||||
general_definition: |-
|
||||
the second step in the TCP three-way handshake, where the server responds to a SYN request with a SYN-ACK packet.
|
||||
- term: SYN-ACK (Synchronize-Acknowledge)
|
||||
general_definition: |-
|
||||
the second step in the TCP three-way handshake, where the server responds to a SYN request with a SYN-ACK packet.
|
||||
|
||||
- term: ACK (Acknowledge)
|
||||
general_definition: |-
|
||||
the final step in the TCP three-way handshake, confirming the establishment of a connection.
|
||||
- term: ACK (Acknowledge)
|
||||
general_definition: |-
|
||||
the final step in the TCP three-way handshake, confirming the establishment of a connection.
|
||||
|
||||
- term: FTP (File Transfer Protocol)
|
||||
general_definition: |-
|
||||
a standard network protocol used for transferring files from one host to another over a TCP-based network.
|
||||
- term: FTP (File Transfer Protocol)
|
||||
general_definition: |-
|
||||
a standard network protocol used for transferring files from one host to another over a TCP-based network.
|
||||
|
||||
- term: FTPS (File Transfer Protocol Secure)
|
||||
general_definition: |-
|
||||
an extension of FTP that adds support for the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) cryptographic protocols.
|
||||
- term: FTPS (File Transfer Protocol Secure)
|
||||
general_definition: |-
|
||||
an extension of FTP that adds support for the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) cryptographic protocols.
|
||||
|
||||
- term: SFTP (Secure File Transfer Protocol)
|
||||
general_definition: |-
|
||||
a secure file transfer protocol that uses the Secure Socket Shell (SSH) protocol for encryption and authentication.
|
||||
- term: SFTP (Secure File Transfer Protocol)
|
||||
general_definition: |-
|
||||
a secure file transfer protocol that uses the Secure Socket Shell (SSH) protocol for encryption and authentication.
|
||||
|
||||
- term: SMTP Server (Simple Mail Transfer Protocol Server)
|
||||
general_definition: |-
|
||||
a server responsible for sending, receiving, and relaying email messages over a network, following the SMTP protocol.
|
||||
- term: SMTP Server (Simple Mail Transfer Protocol Server)
|
||||
general_definition: |-
|
||||
a server responsible for sending, receiving, and relaying email messages over a network, following the SMTP protocol.
|
||||
|
|
|
|||
|
|
@ -1,90 +1,90 @@
|
|||
---
|
||||
productName: Speed
|
||||
entries:
|
||||
- term: page load time
|
||||
general_definition: |-
|
||||
the time it takes for a web page to fully load in a user's browser.
|
||||
- term: page load time
|
||||
general_definition: |-
|
||||
the time it takes for a web page to fully load in a user's browser.
|
||||
|
||||
- term: server response time
|
||||
general_definition: |-
|
||||
the time it takes for a server to respond to a request from a user's browser.
|
||||
- term: server response time
|
||||
general_definition: |-
|
||||
the time it takes for a server to respond to a request from a user's browser.
|
||||
|
||||
- term: latency
|
||||
general_definition: |-
|
||||
the delay between a user action and the corresponding response from the system.
|
||||
- term: latency
|
||||
general_definition: |-
|
||||
the delay between a user action and the corresponding response from the system.
|
||||
|
||||
- term: bandwidth
|
||||
general_definition: |-
|
||||
the maximum rate of data transfer across a network.
|
||||
- term: bandwidth
|
||||
general_definition: |-
|
||||
the maximum rate of data transfer across a network.
|
||||
|
||||
- term: compression
|
||||
general_definition: |-
|
||||
the process of reducing the size of files or data to speed up their transfer over the network.
|
||||
- term: compression
|
||||
general_definition: |-
|
||||
the process of reducing the size of files or data to speed up their transfer over the network.
|
||||
|
||||
- term: minification
|
||||
general_definition: |-
|
||||
the process of removing unnecessary characters from code (such as whitespace or comments) to reduce file size and improve loading times.
|
||||
- term: minification
|
||||
general_definition: |-
|
||||
the process of removing unnecessary characters from code (such as whitespace or comments) to reduce file size and improve loading times.
|
||||
|
||||
- term: lazy loading
|
||||
general_definition: |-
|
||||
loading images or other resources only when they are about to be displayed, rather than loading everything at once.
|
||||
- term: lazy loading
|
||||
general_definition: |-
|
||||
loading images or other resources only when they are about to be displayed, rather than loading everything at once.
|
||||
|
||||
- term: render time
|
||||
general_definition: |-
|
||||
the time it takes for a browser to display a fully rendered web page after receiving the necessary resources.
|
||||
- term: render time
|
||||
general_definition: |-
|
||||
the time it takes for a browser to display a fully rendered web page after receiving the necessary resources.
|
||||
|
||||
- term: brotli compression
|
||||
general_definition: |-
|
||||
brotli compression is a data compression algorithm developed by Google, optimized for web content, and designed to achieve higher compression ratios than traditional algorithms like Gzip.
|
||||
- term: brotli compression
|
||||
general_definition: |-
|
||||
brotli compression is a data compression algorithm developed by Google, optimized for web content, and designed to achieve higher compression ratios than traditional algorithms like Gzip.
|
||||
|
||||
- term: search engine optimization (SEO)
|
||||
general_definition: |-
|
||||
SEO, or search engine optimization, is the practice of optimizing online content to improve its visibility and ranking in search engine results, thereby increasing organic traffic and relevance.
|
||||
- term: search engine optimization (SEO)
|
||||
general_definition: |-
|
||||
SEO, or search engine optimization, is the practice of optimizing online content to improve its visibility and ranking in search engine results, thereby increasing organic traffic and relevance.
|
||||
|
||||
- term: real user monitoring (RUM)
|
||||
general_definition: |-
|
||||
real user monitoring (RUM) is a web performance monitoring technique that collects and analyzes data based on actual user interactions and experiences, providing insights into how users interact with a website or application in real-time.
|
||||
- term: real user monitoring (RUM)
|
||||
general_definition: |-
|
||||
real user monitoring (RUM) is a web performance monitoring technique that collects and analyzes data based on actual user interactions and experiences, providing insights into how users interact with a website or application in real-time.
|
||||
|
||||
- term: synthetic test
|
||||
general_definition: |-
|
||||
a synthetic test is an artificial simulation of user interactions and system behaviors designed to evaluate and measure the performance, responsiveness, and functionality of a website or application under controlled conditions.
|
||||
- term: synthetic test
|
||||
general_definition: |-
|
||||
a synthetic test is an artificial simulation of user interactions and system behaviors designed to evaluate and measure the performance, responsiveness, and functionality of a website or application under controlled conditions.
|
||||
|
||||
- term: core web vitals
|
||||
general_definition: |-
|
||||
core web vitals are a set of user-centric performance metrics, including Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and First Input Delay (FID), used by Google to assess the overall user experience of a webpage.
|
||||
- term: core web vitals
|
||||
general_definition: |-
|
||||
core web vitals are a set of user-centric performance metrics, including Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and First Input Delay (FID), used by Google to assess the overall user experience of a webpage.
|
||||
|
||||
- term: time to first byte (TTFB)
|
||||
general_definition: |-
|
||||
time to first byte (TTFB) is the duration measured from the initiation of a web page request to the moment the first byte of data is received by the user's browser from the web server, indicating the server's initial response time.
|
||||
- term: time to first byte (TTFB)
|
||||
general_definition: |-
|
||||
time to first byte (TTFB) is the duration measured from the initiation of a web page request to the moment the first byte of data is received by the user's browser from the web server, indicating the server's initial response time.
|
||||
|
||||
- term: first contentful paint (FCP)
|
||||
general_definition: |-
|
||||
first contentful paint (FCP) is a web performance metric that measures the time it takes for the first piece of content to be rendered on the screen during the loading of a web page.
|
||||
- term: first contentful paint (FCP)
|
||||
general_definition: |-
|
||||
first contentful paint (FCP) is a web performance metric that measures the time it takes for the first piece of content to be rendered on the screen during the loading of a web page.
|
||||
|
||||
- term: largest contentful paint (LCP)
|
||||
general_definition: |-
|
||||
largest contentful paint (LCP) is a web performance metric that measures the time it takes for the largest content element to be fully rendered and visible to the user during the loading of a web page.
|
||||
- term: largest contentful paint (LCP)
|
||||
general_definition: |-
|
||||
largest contentful paint (LCP) is a web performance metric that measures the time it takes for the largest content element to be fully rendered and visible to the user during the loading of a web page.
|
||||
|
||||
- term: cumulative layout shift (CLS)
|
||||
general_definition: |-
|
||||
cumulative layout shift (CLS) is a web performance metric that quantifies the visual stability of a webpage by measuring the sum of unexpected layout shifts of elements during the page's loading and rendering process.
|
||||
- term: cumulative layout shift (CLS)
|
||||
general_definition: |-
|
||||
cumulative layout shift (CLS) is a web performance metric that quantifies the visual stability of a webpage by measuring the sum of unexpected layout shifts of elements during the page's loading and rendering process.
|
||||
|
||||
- term: time to interactive (TTI)
|
||||
general_definition: |-
|
||||
time to interactive (TTI) is a web performance metric that measures the time it takes for a web page to become fully interactive and responsive to user input, indicating when users can effectively engage with and use the page.
|
||||
- term: time to interactive (TTI)
|
||||
general_definition: |-
|
||||
time to interactive (TTI) is a web performance metric that measures the time it takes for a web page to become fully interactive and responsive to user input, indicating when users can effectively engage with and use the page.
|
||||
|
||||
- term: total blocking time (TBT)
|
||||
general_definition: |-
|
||||
total blocking time (TBT) is a web performance metric that measures the total amount of time between First Contentful Paint (FCP) and Time to Interactive (TTI) where the main thread was blocked for long enough to prevent input responsiveness.
|
||||
- term: total blocking time (TBT)
|
||||
general_definition: |-
|
||||
total blocking time (TBT) is a web performance metric that measures the total amount of time between First Contentful Paint (FCP) and Time to Interactive (TTI) where the main thread was blocked for long enough to prevent input responsiveness.
|
||||
|
||||
- term: speed index
|
||||
general_definition: |-
|
||||
speed index is a web performance metric that quantifies how quickly a user perceives a webpage to load by measuring the visual progression of content rendering over time, providing a comprehensive assessment of the overall user experience during page loading.
|
||||
- term: speed index
|
||||
general_definition: |-
|
||||
speed index is a web performance metric that quantifies how quickly a user perceives a webpage to load by measuring the visual progression of content rendering over time, providing a comprehensive assessment of the overall user experience during page loading.
|
||||
|
||||
- term: interaction to next paint (INP)
|
||||
general_definition: |-
|
||||
interaction to next paint (INP) is a web performance metric that measures the time it takes for a web page to become interactive and respond to user input after the initial paint, providing insights into the user experience during the interaction phase of page loading.
|
||||
- term: interaction to next paint (INP)
|
||||
general_definition: |-
|
||||
interaction to next paint (INP) is a web performance metric that measures the time it takes for a web page to become interactive and respond to user input after the initial paint, providing insights into the user experience during the interaction phase of page loading.
|
||||
|
||||
- term: first input delay (FID)
|
||||
general_definition: |-
|
||||
first input delay (FID) is a web performance metric that measures the delay between a user's first interaction with a page (for example, clicking a button) and the moment the browser responds, indicating the page's interactivity and responsiveness.
|
||||
- term: first input delay (FID)
|
||||
general_definition: |-
|
||||
first input delay (FID) is a web performance metric that measures the delay between a user's first interaction with a page (for example, clicking a button) and the moment the browser responds, indicating the page's interactivity and responsiveness.
|
||||
|
|
|
|||
|
|
@ -1,169 +1,169 @@
|
|||
---
|
||||
productName: SSL/TLS
|
||||
entries:
|
||||
- term: Authenticated Origin Pulls
|
||||
general_definition: |-
|
||||
authenticated Origin Pulls allow origin web servers to validate that a web request came from Cloudflare using TLS client certificate authentication.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: Authenticated Origin Pulls
|
||||
general_definition: |-
|
||||
authenticated Origin Pulls allow origin web servers to validate that a web request came from Cloudflare using TLS client certificate authentication.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: certificate
|
||||
general_definition: |-
|
||||
SSL certificates enable encryption over HTTPS for traffic between a client and a website. SSL certificates contain the website's public key and the website's identity along with related information. Devices attempting to communicate with the origin web server reference the SSL certificate to obtain the public key and verify the server's identity. Cloudflare provides a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for each active Cloudflare domain.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- SSL certificate
|
||||
- CAA record
|
||||
- Certificate Authority
|
||||
- EV certificate
|
||||
- intermediate certificate
|
||||
- primary certificate
|
||||
- root certificate
|
||||
cloudflare_specific: false
|
||||
- term: certificate
|
||||
general_definition: |-
|
||||
SSL certificates enable encryption over HTTPS for traffic between a client and a website. SSL certificates contain the website's public key and the website's identity along with related information. Devices attempting to communicate with the origin web server reference the SSL certificate to obtain the public key and verify the server's identity. Cloudflare provides a [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/) for each active Cloudflare domain.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- SSL certificate
|
||||
- CAA record
|
||||
- Certificate Authority
|
||||
- EV certificate
|
||||
- intermediate certificate
|
||||
- primary certificate
|
||||
- root certificate
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: Certificate Authority (CA)
|
||||
general_definition: |-
|
||||
a CA is a trusted third party that provides SSL certificates for encrypting network traffic.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: Certificate Authority (CA)
|
||||
general_definition: |-
|
||||
a CA is a trusted third party that provides SSL certificates for encrypting network traffic.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: Certification Authority Authorization (CAA) record
|
||||
general_definition: |-
|
||||
a CAA record declares which CAs are allowed to issue an SSL certificate for a domain.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- Certificate Authority
|
||||
cloudflare_specific: false
|
||||
- term: Certification Authority Authorization (CAA) record
|
||||
general_definition: |-
|
||||
a CAA record declares which CAs are allowed to issue an SSL certificate for a domain.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- Certificate Authority
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: certificate packs
|
||||
general_definition: |-
|
||||
certificate packs allow Cloudflare to fallback to a different SSL certificate for browsers that do not support the latest standards. Certificate packs allow Custom SSL certificates to contain different signature algorithms for the same hostnames listed within the SSL certificate without taking up additional Custom SSL certificate quota for your Cloudflare account.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: certificate packs
|
||||
general_definition: |-
|
||||
certificate packs allow Cloudflare to fallback to a different SSL certificate for browsers that do not support the latest standards. Certificate packs allow Custom SSL certificates to contain different signature algorithms for the same hostnames listed within the SSL certificate without taking up additional Custom SSL certificate quota for your Cloudflare account.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: certificate pinning
|
||||
general_definition: |-
|
||||
a security mechanism used to prevent on-path attacks on the Internet by hardcoding information about the certificate that the application expects to receive. If the wrong certificate is received, even if it is trusted by the system, the application will refuse to connect.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: certificate pinning
|
||||
general_definition: |-
|
||||
a security mechanism used to prevent on-path attacks on the Internet by hardcoding information about the certificate that the application expects to receive. If the wrong certificate is received, even if it is trusted by the system, the application will refuse to connect.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: cipher suite
|
||||
general_definition: |-
|
||||
a set of encryption algorithms for establishing a secure communications connection. There are several cipher suites in wide use, and a client and server agree on the cipher suite to use when establishing the TLS connection. Support of multiple cipher suites allows compatibility across various clients.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: cipher suite
|
||||
general_definition: |-
|
||||
a set of encryption algorithms for establishing a secure communications connection. There are several cipher suites in wide use, and a client and server agree on the cipher suite to use when establishing the TLS connection. Support of multiple cipher suites allows compatibility across various clients.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: domain control validation (DCV)
|
||||
general_definition: |-
|
||||
process by which a certificate authority (CA) can verify domain ownership before issuing an SSL/TLS certificate.
|
||||
- term: domain control validation (DCV)
|
||||
general_definition: |-
|
||||
process by which a certificate authority (CA) can verify domain ownership before issuing an SSL/TLS certificate.
|
||||
|
||||
- term: encryption algorithm
|
||||
general_definition: |-
|
||||
an encryption algorithm is a set of mathematical operations performed on data to ensure the data is only understood by the intended recipient.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: encryption algorithm
|
||||
general_definition: |-
|
||||
an encryption algorithm is a set of mathematical operations performed on data to ensure the data is only understood by the intended recipient.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: edge certificate
|
||||
general_definition: |-
|
||||
the SSL/TLS certificates that Cloudflare presents to clients visiting your website or application.
|
||||
- term: edge certificate
|
||||
general_definition: |-
|
||||
the SSL/TLS certificates that Cloudflare presents to clients visiting your website or application.
|
||||
|
||||
Because of [how Cloudflare works](/fundamentals/concepts/how-cloudflare-works/), there can actually be [two certificates involved in a single request](/ssl/concepts/): an edge certificate and an origin certificate.
|
||||
Because of [how Cloudflare works](/fundamentals/concepts/how-cloudflare-works/), there can actually be [two certificates involved in a single request](/ssl/concepts/): an edge certificate and an origin certificate.
|
||||
|
||||
- term: Extended Validation (EV) certificate
|
||||
general_definition: |-
|
||||
EV certificates provide maximum trust to visitors, but require the most validation effort by the CA. EV certificates show the name of the company or organization in the address bar of the visitor’s browser. An EV certificate requires additional documentation by the company or organization in order for the CA to approve the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: Extended Validation (EV) certificate
|
||||
general_definition: |-
|
||||
EV certificates provide maximum trust to visitors, but require the most validation effort by the CA. EV certificates show the name of the company or organization in the address bar of the visitor’s browser. An EV certificate requires additional documentation by the company or organization in order for the CA to approve the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: intermediate certificate
|
||||
general_definition: |-
|
||||
for security purposes, CAs issue intermediate certificates for signing website certificates. Intermediate certificates provide a means for the CA to revoke a single intermediate certificate, thus affecting only a small subset of website certificates.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: intermediate certificate
|
||||
general_definition: |-
|
||||
for security purposes, CAs issue intermediate certificates for signing website certificates. Intermediate certificates provide a means for the CA to revoke a single intermediate certificate, thus affecting only a small subset of website certificates.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: mTLS (mutual TLS)
|
||||
general_definition: |-
|
||||
mTLS is a common security practice that uses TLS certificates to ensure that traffic between a client and server is secure and trusted in both directions.
|
||||
associated_products:
|
||||
- API Shield
|
||||
- Cloudflare One
|
||||
related_terms:
|
||||
- TLS
|
||||
cloudflare_specific: false
|
||||
- term: mTLS (mutual TLS)
|
||||
general_definition: |-
|
||||
mTLS is a common security practice that uses TLS certificates to ensure that traffic between a client and server is secure and trusted in both directions.
|
||||
associated_products:
|
||||
- API Shield
|
||||
- Cloudflare One
|
||||
related_terms:
|
||||
- TLS
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: origin certificate
|
||||
general_definition: |-
|
||||
a Cloudflare Origin Certificate is a free SSL/TLS certificate issued by Cloudflare that can be installed on your origin server to facilitate making sure your data is encrypted in transit from Cloudflare to your origin server using HTTPS.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: origin certificate
|
||||
general_definition: |-
|
||||
a Cloudflare Origin Certificate is a free SSL/TLS certificate issued by Cloudflare that can be installed on your origin server to facilitate making sure your data is encrypted in transit from Cloudflare to your origin server using HTTPS.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: Organization Validated (OV) certificate
|
||||
general_definition: |-
|
||||
OV certificates are used by corporations or governments to portray an extra layer of confidence for their visitors. Rather than just validating domain ownership, the CA also validates the company’s registration using qualified independent information sources. The organization’s name is listed in the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: Organization Validated (OV) certificate
|
||||
general_definition: |-
|
||||
OV certificates are used by corporations or governments to portray an extra layer of confidence for their visitors. Rather than just validating domain ownership, the CA also validates the company’s registration using qualified independent information sources. The organization’s name is listed in the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: primary certificate / secondary certificate
|
||||
general_definition: |-
|
||||
Primary and secondary indicates the order in which Custom SSL certificates were uploaded to Cloudflare. The primary certificate is the first certificate added to a pack. The primary certificate defines the hostnames covered by the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
- term: primary certificate / secondary certificate
|
||||
general_definition: |-
|
||||
Primary and secondary indicates the order in which Custom SSL certificates were uploaded to Cloudflare. The primary certificate is the first certificate added to a pack. The primary certificate defines the hostnames covered by the certificate.
|
||||
associated_products: []
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: public key / private key
|
||||
general_definition: |-
|
||||
SSL public and private keys are essentially long strings of characters used for encrypting and decrypting data. Data encrypted with the public key can only be decrypted with the private key, and vice versa. Private keys are kept secret and unshared.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- certificate
|
||||
cloudflare_specific: false
|
||||
- term: public key / private key
|
||||
general_definition: |-
|
||||
SSL public and private keys are essentially long strings of characters used for encrypting and decrypting data. Data encrypted with the public key can only be decrypted with the private key, and vice versa. Private keys are kept secret and unshared.
|
||||
associated_products: []
|
||||
related_terms:
|
||||
- certificate
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: root certificate
|
||||
general_definition: |-
|
||||
a root certificate is generated by a CA and is used to sign certificates. Every browser includes a root store of trusted root certificates. Any certificate signed with the private key of a root certificate is automatically trusted by a browser.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- term: root certificate
|
||||
general_definition: |-
|
||||
a root certificate is generated by a CA and is used to sign certificates. Every browser includes a root store of trusted root certificates. Any certificate signed with the private key of a root certificate is automatically trusted by a browser.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
related_terms: []
|
||||
cloudflare_specific: false
|
||||
|
||||
- term: Secure Sockets Layer (SSL)
|
||||
general_definition: |-
|
||||
SSL was a widely used cryptographic protocol for providing data security for Internet communications. SSL was superseded by TLS; however, most people still refer to Internet cryptographic protocols as SSL.
|
||||
- term: Secure Sockets Layer (SSL)
|
||||
general_definition: |-
|
||||
SSL was a widely used cryptographic protocol for providing data security for Internet communications. SSL was superseded by TLS; however, most people still refer to Internet cryptographic protocols as SSL.
|
||||
|
||||
- term: Server Name Indication (SNI)
|
||||
general_definition: |-
|
||||
SNI allows a server to host multiple TLS Certificates for multiple websites using a single IP address. SNI adds the website hostname in the TLS handshake to inform the server which website to present when using shared IPs.
|
||||
- term: Server Name Indication (SNI)
|
||||
general_definition: |-
|
||||
SNI allows a server to host multiple TLS Certificates for multiple websites using a single IP address. SNI adds the website hostname in the TLS handshake to inform the server which website to present when using shared IPs.
|
||||
|
||||
Cloudflare uses SNI for all Universal SSL certificates.
|
||||
Cloudflare uses SNI for all Universal SSL certificates.
|
||||
|
||||
- term: Subject Alternative Names (SANs)
|
||||
general_definition: |-
|
||||
The SAN field of an SSL certificate specifies additional hostnames (sites, IP addresses, common names, subdomains, apex domains, etc.) protected by a single SSL Certificate.
|
||||
- term: Subject Alternative Names (SANs)
|
||||
general_definition: |-
|
||||
The SAN field of an SSL certificate specifies additional hostnames (sites, IP addresses, common names, subdomains, apex domains, etc.) protected by a single SSL Certificate.
|
||||
|
||||
- term: TLS (Transport Layer Security)
|
||||
general_definition: |-
|
||||
TLS is a cryptographic protocol that ensures data security over a computer network, such as the Internet. It encrypts the data that is transmitted between a user's computer and a web server.
|
||||
- term: TLS (Transport Layer Security)
|
||||
general_definition: |-
|
||||
TLS is a cryptographic protocol that ensures data security over a computer network, such as the Internet. It encrypts the data that is transmitted between a user's computer and a web server.
|
||||
|
||||
- term: Universal SSL certificate
|
||||
general_definition: |-
|
||||
by default, Cloudflare issues — and renews — free, unshared, publicly trusted SSL certificates to all domains [added to](/fundamentals/setup/manage-domains/add-site/) and [activated on](/dns/zone-setups/reference/domain-status/) Cloudflare.
|
||||
- term: Universal SSL certificate
|
||||
general_definition: |-
|
||||
by default, Cloudflare issues — and renews — free, unshared, publicly trusted SSL certificates to all domains [added to](/fundamentals/setup/manage-domains/add-site/) and [activated on](/dns/zone-setups/reference/domain-status/) Cloudflare.
|
||||
|
||||
- term: validation level
|
||||
general_definition: |-
|
||||
the level to which a certificate authority validates domain ownership before issuing an SSL/TLS certificate.
|
||||
- term: validation level
|
||||
general_definition: |-
|
||||
the level to which a certificate authority validates domain ownership before issuing an SSL/TLS certificate.
|
||||
|
||||
The different certificate validation levels are DV (Domain Validated), OV (Organization Validated), or EV (Extended Validation).
|
||||
The different certificate validation levels are DV (Domain Validated), OV (Organization Validated), or EV (Extended Validation).
|
||||
|
|
|
|||
|
|
@ -2,4 +2,4 @@ productName: Style Guide
|
|||
entries:
|
||||
- term: example
|
||||
general_definition: |-
|
||||
Hello, world! You can use **Markdown** features inside of your `tooltips`.
|
||||
Hello, world! You can use **Markdown** features inside of your `tooltips`.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
productName: Turnstile
|
||||
entries:
|
||||
- term: CAPTCHA
|
||||
general_definition: |-
|
||||
A CAPTCHA test is designed to determine if an online user is really a human and not a bot. CAPTCHA is an acronym that stands for "Completely Automated Public Turing test to tell Computers and Humans Apart."
|
||||
- term: CAPTCHA
|
||||
general_definition: |-
|
||||
A CAPTCHA test is designed to determine if an online user is really a human and not a bot. CAPTCHA is an acronym that stands for "Completely Automated Public Turing test to tell Computers and Humans Apart."
|
||||
|
||||
- term: secret key
|
||||
general_definition: |-
|
||||
The secret key allows communication between your application backend and the Cloudflare Turnstile server to validate the widget response.
|
||||
- term: secret key
|
||||
general_definition: |-
|
||||
The secret key allows communication between your application backend and the Cloudflare Turnstile server to validate the widget response.
|
||||
|
||||
- term: sitekey
|
||||
general_definition: |-
|
||||
The sitekey is used to invoke Turnstile on your site.
|
||||
- term: sitekey
|
||||
general_definition: |-
|
||||
The sitekey is used to invoke Turnstile on your site.
|
||||
|
|
|
|||
|
|
@ -1,61 +1,61 @@
|
|||
---
|
||||
productName: WAF
|
||||
entries:
|
||||
- term: allowlist
|
||||
general_definition: |-
|
||||
an allowlist is a list of items (usually websites, IP addresses, email addresses, etc.) that are permitted to access a system.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
- term: allowlist
|
||||
general_definition: |-
|
||||
an allowlist is a list of items (usually websites, IP addresses, email addresses, etc.) that are permitted to access a system.
|
||||
associated_products:
|
||||
- DDoS Protection
|
||||
|
||||
- term: attack score
|
||||
general_definition: |-
|
||||
a number from 1 (likely malicious) to 99 (likely clean) classifying how likely an incoming request is malicious or not. Allows you to detect new attack techniques before they are publicly known.
|
||||
- term: attack score
|
||||
general_definition: |-
|
||||
a number from 1 (likely malicious) to 99 (likely clean) classifying how likely an incoming request is malicious or not. Allows you to detect new attack techniques before they are publicly known.
|
||||
|
||||
- term: blocklist
|
||||
general_definition: |-
|
||||
a blocklist is a list of items (usually websites, IP addresses, email addresses, etc.) that are prevented from accessing a system.
|
||||
- term: blocklist
|
||||
general_definition: |-
|
||||
a blocklist is a list of items (usually websites, IP addresses, email addresses, etc.) that are prevented from accessing a system.
|
||||
|
||||
- term: content object
|
||||
general_definition: |-
|
||||
a content object is any binary part of a request body (as detected by Cloudflare systems) that does not match any of the following content types: `text/html`, `text/x-shellscript`, `application/json`, `text/csv`, or `text/xml`.
|
||||
- term: content object
|
||||
general_definition: |-
|
||||
a content object is any binary part of a request body (as detected by Cloudflare systems) that does not match any of the following content types: `text/html`, `text/x-shellscript`, `application/json`, `text/csv`, or `text/xml`.
|
||||
|
||||
- term: credential stuffing
|
||||
general_definition: |-
|
||||
credential stuffing is the automated injection of stolen username and password pairs (known as "credentials") into website login forms, trying to gain access to user accounts.
|
||||
- term: credential stuffing
|
||||
general_definition: |-
|
||||
credential stuffing is the automated injection of stolen username and password pairs (known as "credentials") into website login forms, trying to gain access to user accounts.
|
||||
|
||||
- term: exposed credentials
|
||||
general_definition: |-
|
||||
exposed credentials refers to sensitive authentication information disclosed in some way (for example, due to misconfigurations, data breaches, or simple human error), allowing other parties to gain access to digital resources.
|
||||
- term: exposed credentials
|
||||
general_definition: |-
|
||||
exposed credentials refers to sensitive authentication information disclosed in some way (for example, due to misconfigurations, data breaches, or simple human error), allowing other parties to gain access to digital resources.
|
||||
|
||||
Credentials may include usernames, passwords, API keys, authentication tokens, or private keys.
|
||||
Credentials may include usernames, passwords, API keys, authentication tokens, or private keys.
|
||||
|
||||
- term: firewall
|
||||
general_definition: |-
|
||||
a firewall is a security system that monitors and controls network traffic based on a set of security rules.
|
||||
associated_products:
|
||||
- Magic Firewall
|
||||
- term: firewall
|
||||
general_definition: |-
|
||||
a firewall is a security system that monitors and controls network traffic based on a set of security rules.
|
||||
associated_products:
|
||||
- Magic Firewall
|
||||
|
||||
- term: mitigated request
|
||||
general_definition: |-
|
||||
a request to which Cloudflare applied a terminating action such as block or challenge.
|
||||
- term: mitigated request
|
||||
general_definition: |-
|
||||
a request to which Cloudflare applied a terminating action such as block or challenge.
|
||||
|
||||
- term: paranoia level
|
||||
general_definition: |-
|
||||
classifies rules of the OWASP managed ruleset according to their aggressiveness.
|
||||
- term: paranoia level
|
||||
general_definition: |-
|
||||
classifies rules of the OWASP managed ruleset according to their aggressiveness.
|
||||
|
||||
- term: rate limiting
|
||||
general_definition: |-
|
||||
rate limiting is a technique used in computer systems to control the rate at which requests are processed. It can be used as a security measure to prevent attacks, or to limit resource usage in your origin servers.
|
||||
- term: rate limiting
|
||||
general_definition: |-
|
||||
rate limiting is a technique used in computer systems to control the rate at which requests are processed. It can be used as a security measure to prevent attacks, or to limit resource usage in your origin servers.
|
||||
|
||||
- term: SIEM
|
||||
general_definition: |-
|
||||
a Security Information and Event Management (SIEM) solution collects, analyzes, and correlates data to help manage security incidents, detect anomalies, and meet compliance requirements.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- Area 1
|
||||
- term: SIEM
|
||||
general_definition: |-
|
||||
a Security Information and Event Management (SIEM) solution collects, analyzes, and correlates data to help manage security incidents, detect anomalies, and meet compliance requirements.
|
||||
associated_products:
|
||||
- Cloudflare One
|
||||
- Area 1
|
||||
|
||||
- term: threat score
|
||||
general_definition: |-
|
||||
the threat score is a score from 0 (zero risk) to 100 (high risk) classifying the IP reputation of a visitor.
|
||||
- term: threat score
|
||||
general_definition: |-
|
||||
the threat score is a score from 0 (zero risk) to 100 (high risk) classifying the IP reputation of a visitor.
|
||||
|
||||
IP reputation is calculated based on Project Honeypot, external public IP information, as well as internal threat intelligence from WAF managed rules and DDoS.
|
||||
IP reputation is calculated based on Project Honeypot, external public IP information, as well as internal threat intelligence from WAF managed rules and DDoS.
|
||||
|
|
|
|||
|
|
@ -1,44 +1,44 @@
|
|||
---
|
||||
productName: Waiting Room
|
||||
entries:
|
||||
- term: traffic management
|
||||
general_definition: |-
|
||||
the process of controlling and optimizing the flow of network data to ensure efficient and reliable communication.
|
||||
- term: traffic management
|
||||
general_definition: |-
|
||||
the process of controlling and optimizing the flow of network data to ensure efficient and reliable communication.
|
||||
|
||||
- term: legitimate traffic
|
||||
general_definition: |-
|
||||
legitimate traffic refers to authorized and permissible network activity, data transmissions, or communications that adhere to established norms and rules within a given system or network.
|
||||
- term: legitimate traffic
|
||||
general_definition: |-
|
||||
legitimate traffic refers to authorized and permissible network activity, data transmissions, or communications that adhere to established norms and rules within a given system or network.
|
||||
|
||||
- term: downtime
|
||||
general_definition: |-
|
||||
downtime is the duration during which a system, service, or equipment is not operational or unavailable for use.
|
||||
- term: downtime
|
||||
general_definition: |-
|
||||
downtime is the duration during which a system, service, or equipment is not operational or unavailable for use.
|
||||
|
||||
- term: error page
|
||||
general_definition: |-
|
||||
an error page is a webpage shown to users when they try to access a specific webpage or resource that is unavailable due to a server error, broken link, or other issues. It typically includes details about the encountered error and offers potential solutions or guidance to help users navigate the problem.
|
||||
- term: error page
|
||||
general_definition: |-
|
||||
an error page is a webpage shown to users when they try to access a specific webpage or resource that is unavailable due to a server error, broken link, or other issues. It typically includes details about the encountered error and offers potential solutions or guidance to help users navigate the problem.
|
||||
|
||||
- term: non-browser traffic
|
||||
general_definition: |-
|
||||
non-browser traffic refers to data exchanges and communication occurring between devices or systems that do not involve web browsers, such as a mobile app or web apps.
|
||||
- term: non-browser traffic
|
||||
general_definition: |-
|
||||
non-browser traffic refers to data exchanges and communication occurring between devices or systems that do not involve web browsers, such as a mobile app or web apps.
|
||||
|
||||
- term: JSON-friendly
|
||||
general_definition: |-
|
||||
JSON-friendly refers to data or formats that are easily and naturally represented in JSON (JavaScript Object Notation), a lightweight data interchange format, without requiring complex transformations or modifications.
|
||||
- term: JSON-friendly
|
||||
general_definition: |-
|
||||
JSON-friendly refers to data or formats that are easily and naturally represented in JSON (JavaScript Object Notation), a lightweight data interchange format, without requiring complex transformations or modifications.
|
||||
|
||||
- term: iFrame
|
||||
general_definition: |-
|
||||
an iFrame, short for Inline Frame, is an HTML element used to embed and display external content within a webpage, allowing the incorporation of another document or web page seamlessly within the main document.
|
||||
- term: iFrame
|
||||
general_definition: |-
|
||||
an iFrame, short for Inline Frame, is an HTML element used to embed and display external content within a webpage, allowing the incorporation of another document or web page seamlessly within the main document.
|
||||
|
||||
- term: Set-Cookie
|
||||
general_definition: |-
|
||||
Set-Cookie is an HTTP header used by web servers to send a cookie to a user's browser during an HTTP response, enabling the server to store information on the client side, often used for session management and user preferences.
|
||||
associated_products:
|
||||
- Cache
|
||||
- term: Set-Cookie
|
||||
general_definition: |-
|
||||
Set-Cookie is an HTTP header used by web servers to send a cookie to a user's browser during an HTTP response, enabling the server to store information on the client side, often used for session management and user preferences.
|
||||
associated_products:
|
||||
- Cache
|
||||
|
||||
- term: SEO crawlers
|
||||
general_definition: |-
|
||||
SEO crawlers, or web crawlers, are automated programs employed by search engines to systematically browse and index web content, gathering information about the structure and relevance of pages to determine search result rankings.
|
||||
- term: SEO crawlers
|
||||
general_definition: |-
|
||||
SEO crawlers, or web crawlers, are automated programs employed by search engines to systematically browse and index web content, gathering information about the structure and relevance of pages to determine search result rankings.
|
||||
|
||||
- term: virtual waiting room
|
||||
general_definition: |-
|
||||
a virtual waiting room is an online system or feature that manages and controls access to a website or service during periods of high traffic, preventing server overload by placing users in a queue until they can be accommodated, ensuring a more equitable and efficient user experience.
|
||||
- term: virtual waiting room
|
||||
general_definition: |-
|
||||
a virtual waiting room is an online system or feature that manages and controls access to a website or service during periods of high traffic, preventing server overload by placing users in a queue until they can be accommodated, ensuring a more equitable and efficient user experience.
|
||||
|
|
|
|||
|
|
@ -1,135 +1,134 @@
|
|||
---
|
||||
productName: Workers
|
||||
entries:
|
||||
- term: Auxiliary Worker
|
||||
general_definition: |-
|
||||
A Worker created locally via the [Workers Vitest integration](/workers/testing/vitest-integration/) that runs in a separate isolate to the test runner, with a different global scope.
|
||||
|
||||
- term: Auxiliary Worker
|
||||
general_definition: |-
|
||||
A Worker created locally via the [Workers Vitest integration](/workers/testing/vitest-integration/) that runs in a separate isolate to the test runner, with a different global scope.
|
||||
- term: binding
|
||||
general_definition: |-
|
||||
[Bindings](/workers/runtime-apis/bindings/) allow your Workers to interact with resources on the Cloudflare Developer Platform.
|
||||
|
||||
- term: binding
|
||||
general_definition: |-
|
||||
[Bindings](/workers/runtime-apis/bindings/) allow your Workers to interact with resources on the Cloudflare Developer Platform.
|
||||
- term: Cron Triggers
|
||||
general_definition: |-
|
||||
[Cron Triggers](/workers/configuration/cron-triggers/) allow users to map a cron expression to a Worker using a [`scheduled()` handler](/workers/runtime-apis/handlers/scheduled/) that enables Workers to be executed on a schedule.
|
||||
|
||||
- term: Cron Triggers
|
||||
general_definition: |-
|
||||
[Cron Triggers](/workers/configuration/cron-triggers/) allow users to map a cron expression to a Worker using a [`scheduled()` handler](/workers/runtime-apis/handlers/scheduled/) that enables Workers to be executed on a schedule.
|
||||
- term: C3
|
||||
general_definition: |-
|
||||
[C3](/learning-paths/workers/get-started/c3-and-wrangler/) is a command-line tool designed to help you set up and deploy new applications to Cloudflare.
|
||||
|
||||
- term: C3
|
||||
general_definition: |-
|
||||
[C3](/learning-paths/workers/get-started/c3-and-wrangler/) is a command-line tool designed to help you set up and deploy new applications to Cloudflare.
|
||||
- term: CPU time
|
||||
general_definition: |-
|
||||
[CPU time](/workers/platform/limits/#cpu-time) is the amount of time the central processing unit (CPU) actually spends doing work, during a given request.
|
||||
|
||||
- term: CPU time
|
||||
general_definition: |-
|
||||
[CPU time](/workers/platform/limits/#cpu-time) is the amount of time the central processing unit (CPU) actually spends doing work, during a given request.
|
||||
- term: deployment
|
||||
general_definition: |-
|
||||
[Deployments](/workers/configuration/versions-and-deployments/#deployments) track the version(s) of your Worker that are actively serving traffic.
|
||||
|
||||
- term: deployment
|
||||
general_definition: |-
|
||||
[Deployments](/workers/configuration/versions-and-deployments/#deployments) track the version(s) of your Worker that are actively serving traffic.
|
||||
- term: Durable Objects
|
||||
general_definition: |-
|
||||
[Durable Objects](/durable-objects/) is a globally distributed coordination API with strongly consistent storage.
|
||||
associated_products:
|
||||
- Durable Objects
|
||||
|
||||
- term: Durable Objects
|
||||
general_definition: |-
|
||||
[Durable Objects](/durable-objects/) is a globally distributed coordination API with strongly consistent storage.
|
||||
associated_products:
|
||||
- Durable Objects
|
||||
- term: duration
|
||||
general_definition: |-
|
||||
[Duration](/workers/platform/limits/#duration) is a measurement of wall-clock time — the total amount of time from the start to end of an invocation of a Worker.
|
||||
|
||||
- term: duration
|
||||
general_definition: |-
|
||||
[Duration](/workers/platform/limits/#duration) is a measurement of wall-clock time — the total amount of time from the start to end of an invocation of a Worker.
|
||||
- term: D1
|
||||
general_definition: |-
|
||||
[D1](/d1/) is Cloudflare's native serverless database.
|
||||
associated_products:
|
||||
- D1
|
||||
|
||||
- term: D1
|
||||
general_definition: |-
|
||||
[D1](/d1/) is Cloudflare's native serverless database.
|
||||
associated_products:
|
||||
- D1
|
||||
- term: environment
|
||||
general_definition: |-
|
||||
[Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configuration for each environment. Only available for use with `wrangler.toml`.
|
||||
|
||||
- term: environment
|
||||
general_definition: |-
|
||||
[Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configuration for each environment. Only available for use with `wrangler.toml`.
|
||||
- term: environment variable
|
||||
general_definition: |-
|
||||
[Environment variables](/workers/configuration/environment-variables/) are a type of binding that allow you to attach text strings or JSON values to your Worker.
|
||||
|
||||
- term: environment variable
|
||||
general_definition: |-
|
||||
[Environment variables](/workers/configuration/environment-variables/) are a type of binding that allow you to attach text strings or JSON values to your Worker.
|
||||
- term: handler
|
||||
general_definition: |-
|
||||
[Handlers](/workers/runtime-apis/handlers/) are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker.
|
||||
|
||||
- term: handler
|
||||
general_definition: |-
|
||||
[Handlers](/workers/runtime-apis/handlers/) are methods on Workers that can receive and process external inputs, and can be invoked from outside your Worker.
|
||||
- term: isolate
|
||||
general_definition: |-
|
||||
[Isolates](/workers/reference/how-workers-works/#isolates) are lightweight contexts that provide your code with variables it can access and a safe environment to be executed within.
|
||||
|
||||
- term: isolate
|
||||
general_definition: |-
|
||||
[Isolates](/workers/reference/how-workers-works/#isolates) are lightweight contexts that provide your code with variables it can access and a safe environment to be executed within.
|
||||
- term: KV
|
||||
general_definition: |-
|
||||
[Workers KV](/kv/) is Cloudflare's key-value data storage.
|
||||
associated_products:
|
||||
- KV
|
||||
|
||||
- term: KV
|
||||
general_definition: |-
|
||||
[Workers KV](/kv/) is Cloudflare's key-value data storage.
|
||||
associated_products:
|
||||
- KV
|
||||
- term: module Worker
|
||||
general_definition: |-
|
||||
Refers to a Worker written in [module syntax](/workers/reference/migrate-to-module-workers/).
|
||||
|
||||
- term: module Worker
|
||||
general_definition: |-
|
||||
Refers to a Worker written in [module syntax](/workers/reference/migrate-to-module-workers/).
|
||||
- term: origin
|
||||
general_definition: |-
|
||||
[Origin](https://www.cloudflare.com/learning/cdn/glossary/origin-server/) generally refers to the web server behind Cloudflare where your application is hosted.
|
||||
|
||||
- term: origin
|
||||
general_definition: |-
|
||||
[Origin](https://www.cloudflare.com/learning/cdn/glossary/origin-server/) generally refers to the web server behind Cloudflare where your application is hosted.
|
||||
- term: Pages
|
||||
general_definition: |-
|
||||
[Cloudflare Pages](/pages/) is Cloudflare's product offering for building and deploying full-stack applications.
|
||||
associated_products:
|
||||
- Pages
|
||||
|
||||
- term: Pages
|
||||
general_definition: |-
|
||||
[Cloudflare Pages](/pages/) is Cloudflare's product offering for building and deploying full-stack applications.
|
||||
associated_products:
|
||||
- Pages
|
||||
- term: Queues
|
||||
general_definition: |-
|
||||
[Queues](/queues/) integrates with Cloudflare Workers and enables you to build applications that can guarantee delivery.
|
||||
associated_products:
|
||||
- Queues
|
||||
|
||||
- term: Queues
|
||||
general_definition: |-
|
||||
[Queues](/queues/) integrates with Cloudflare Workers and enables you to build applications that can guarantee delivery.
|
||||
associated_products:
|
||||
- Queues
|
||||
- term: rollback
|
||||
general_definition: |-
|
||||
[Rollbacks](/workers/configuration/versions-and-deployments/rollbacks/) are a way to deploy an older deployment to the Cloudflare global network.
|
||||
|
||||
- term: rollback
|
||||
general_definition: |-
|
||||
[Rollbacks](/workers/configuration/versions-and-deployments/rollbacks/) are a way to deploy an older deployment to the Cloudflare global network.
|
||||
- term: R2
|
||||
general_definition: |-
|
||||
[R2](/r2/) is an S3-compatible distributed object storage designed to eliminate the obstacles of sharing data across clouds.
|
||||
associated_products:
|
||||
- R2
|
||||
|
||||
- term: R2
|
||||
general_definition: |-
|
||||
[R2](/r2/) is an S3-compatible distributed object storage designed to eliminate the obstacles of sharing data across clouds.
|
||||
associated_products:
|
||||
- R2
|
||||
- term: secret
|
||||
general_definition: |-
|
||||
[Secrets](/workers/configuration/secrets/) are a type of binding that allow you to attach encrypted text values to your Worker.
|
||||
|
||||
- term: secret
|
||||
general_definition: |-
|
||||
[Secrets](/workers/configuration/secrets/) are a type of binding that allow you to attach encrypted text values to your Worker.
|
||||
- term: service Worker
|
||||
general_definition: |-
|
||||
Refers to a Worker written in [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) [syntax](/workers/reference/migrate-to-module-workers/).
|
||||
|
||||
- term: service Worker
|
||||
general_definition: |-
|
||||
Refers to a Worker written in [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) [syntax](/workers/reference/migrate-to-module-workers/).
|
||||
- term: subrequest
|
||||
general_definition: |-
|
||||
A subrequest is any request that a Worker makes to either Internet resources using the [Fetch API](/workers/runtime-apis/fetch/) or requests to other Cloudflare services like [R2](/r2/), [KV](/kv/), or [D1](/d1/).
|
||||
|
||||
- term: subrequest
|
||||
general_definition: |-
|
||||
A subrequest is any request that a Worker makes to either Internet resources using the [Fetch API](/workers/runtime-apis/fetch/) or requests to other Cloudflare services like [R2](/r2/), [KV](/kv/), or [D1](/d1/).
|
||||
- term: Tail Worker
|
||||
general_definition: |-
|
||||
A [Tail Worker](/workers/observability/logging/tail-workers/) receives information about the execution of other Workers (known as producer Workers), such as HTTP statuses, data passed to `console.log()` or uncaught exceptions.
|
||||
|
||||
- term: Tail Worker
|
||||
general_definition: |-
|
||||
A [Tail Worker](/workers/observability/logging/tail-workers/) receives information about the execution of other Workers (known as producer Workers), such as HTTP statuses, data passed to `console.log()` or uncaught exceptions.
|
||||
- term: version
|
||||
general_definition: |-
|
||||
A [version](/workers/configuration/versions-and-deployments/#versions) is defined by the state of code as well as the state of configuration in a Worker's `wrangler.toml` file.
|
||||
|
||||
- term: version
|
||||
general_definition: |-
|
||||
A [version](/workers/configuration/versions-and-deployments/#versions) is defined by the state of code as well as the state of configuration in a Worker's `wrangler.toml` file.
|
||||
- term: V8
|
||||
general_definition: |-
|
||||
Chrome V8 is a [JavaScript engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/), which means that it [executes JavaScript code](/workers/reference/how-workers-works/).
|
||||
|
||||
- term: V8
|
||||
general_definition: |-
|
||||
Chrome V8 is a [JavaScript engine](https://www.cloudflare.com/learning/serverless/glossary/what-is-chrome-v8/), which means that it [executes JavaScript code](/workers/reference/how-workers-works/).
|
||||
- term: wall-clock time
|
||||
general_definition: |-
|
||||
[Wall-clock time](/workers/platform/limits/#duration) is the total amount of time from the start to end of an invocation of a Worker.
|
||||
|
||||
- term: wall-clock time
|
||||
general_definition: |-
|
||||
[Wall-clock time](/workers/platform/limits/#duration) is the total amount of time from the start to end of an invocation of a Worker.
|
||||
- term: workerd
|
||||
general_definition: |-
|
||||
[`workerd`](https://github.com/cloudflare/workerd?cf_target_id=D15F29F105B3A910EF4B2ECB12D02E2A) is a JavaScript / Wasm server runtime based on the same code that powers Cloudflare Workers.
|
||||
|
||||
- term: workerd
|
||||
general_definition: |-
|
||||
[`workerd`](https://github.com/cloudflare/workerd?cf_target_id=D15F29F105B3A910EF4B2ECB12D02E2A) is a JavaScript / Wasm server runtime based on the same code that powers Cloudflare Workers.
|
||||
- term: Wrangler
|
||||
general_definition: |-
|
||||
[Wrangler](/learning-paths/workers/get-started/c3-and-wrangler/) is the Cloudflare Developer Platform command-line interface (CLI) that allows you to manage projects, such as Workers, created from the Cloudflare Developer Platform product offering.
|
||||
|
||||
- term: Wrangler
|
||||
general_definition: |-
|
||||
[Wrangler](/learning-paths/workers/get-started/c3-and-wrangler/) is the Cloudflare Developer Platform command-line interface (CLI) that allows you to manage projects, such as Workers, created from the Cloudflare Developer Platform product offering.
|
||||
|
||||
- term: wrangler.toml
|
||||
general_definition: |-
|
||||
The [configuration](/workers/wrangler/configuration/) file used to customize the development and deployment setup for a Worker or a Pages Function.
|
||||
- term: wrangler.toml
|
||||
general_definition: |-
|
||||
The [configuration](/workers/wrangler/configuration/) file used to customize the development and deployment setup for a Worker or a Pages Function.
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
|
|
@ -95,4 +95,4 @@ tools:
|
|||
environment_variable: "ZOLA_VERSION"
|
||||
build_environment:
|
||||
operating_system: "Ubuntu `20.04.5`"
|
||||
architecture: "x86_64"
|
||||
architecture: "x86_64"
|
||||
|
|
|
|||
|
|
@ -64,4 +64,4 @@ tools:
|
|||
environment_variable: "BUN_VERSION"
|
||||
build_environment:
|
||||
operating_system: "Ubuntu `22.04.2`"
|
||||
architecture: "x86_64"
|
||||
architecture: "x86_64"
|
||||
|
|
|
|||
|
|
@ -143,4 +143,4 @@ build_configs:
|
|||
display_name: Zola
|
||||
build_command: zola build
|
||||
build_output_directory: public
|
||||
icon: /icons/framework-icons/logo-zola.svg
|
||||
icon: /icons/framework-icons/logo-zola.svg
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Access
|
||||
group: Cloudflare One
|
||||
url: /cloudflare-one/policies/access/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Account and Billing
|
||||
group: Cloudflare essentials
|
||||
url: /fundamentals/subscriptions-and-billing/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Browser Isolation
|
||||
group: Cloudflare One
|
||||
url: /cloudflare-one/policies/browser-isolation/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Cache Reserve
|
||||
group: Application performance
|
||||
url: /cache/advanced-configuration/cache-reserve/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: CASB
|
||||
group: Cloudflare One
|
||||
url: /cloudflare-one/applications/scan-apps/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -9,4 +9,4 @@ product:
|
|||
preview_tryout: true
|
||||
|
||||
resources:
|
||||
dashboard_link: https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/custom-hostnames
|
||||
dashboard_link: https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/custom-hostnames
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Cloudflare Tunnel
|
||||
group: Cloudflare One
|
||||
url: /cloudflare-one/connections/connect-networks/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -6,4 +6,4 @@ product:
|
|||
additional_groups: [Analytics]
|
||||
url: /cloudflare-one/insights/dex/
|
||||
grid_placeholder: true
|
||||
wrap: true
|
||||
wrap: true
|
||||
|
|
|
|||
|
|
@ -4,4 +4,4 @@ product:
|
|||
title: Data Loss Prevention
|
||||
group: Cloudflare One
|
||||
url: /cloudflare-one/policies/data-loss-prevention/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@ product:
|
|||
group: Application performance
|
||||
additional_groups: [Application security]
|
||||
url: /dns/dns-firewall/
|
||||
grid_placeholder: true
|
||||
grid_placeholder: true
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue