边缘加速

站点加速
- 概述
- 快速导入导出站点配置
- 访问控制
  - Token 鉴权
  - 认证方法A
  - 认证方法B
  - 认证方法C
  - 认证方法D
  - 认证方法V
- 智能加速
- 文件优化
  - 智能压缩
- 网络优化
  - HTTP/2
  - HTTP/3(QUIC)
    - 概述
    - 启用 HTTP/3
    - QUIC SDK
      - SDK 概览
      - SDK 下载和集成指引
      - 代码示例
        Android
        iOS
      - API 文档
        Android
        iOS
  - IPv6 访问
  - 最大上传大小
  - WebSocket
  - 携带客户端 IP 头部回源
  - 携带客户端 IP 地理位置头部回源
  - 开启 gRPC
- URL 重写
  - 访问 URL 重定向
  - 回源 URL 重写
- 修改头部
  - 修改 HTTP 节点响应头
  - 修改 HTTP 回源请求头
- 自定义错误页面
- 请求与响应行为
  - HTTP响应
  - 请求处理顺序
  - EdgeOne 默认 HTTP 回源请求头
  - EdgeOne 默认 HTTP 响应头
  - HTTP限制
- 媒体服务
  - 音视频预拉取
  - 实时图片处理
  - 实时媒体处理
  - 点播媒体源
四层代理
- 概述
- 新建四层代理实例
- 修改四层代理实例配置
- 停用/删除四层代理实例
- 批量配置转发规则
- 获取客户端真实IP
  - 通过 TOA 获取 TCP 协议客户端真实 IP
  - 通过 Proxy Protocol V1/V2 协议获取客户端真实 IP
    - 概述
    - 方式一：通过 Nginx 获取客户端真实 IP
    - 方式二：在业务服务器解析客户端真实 IP
    - Proxy Protocol V1/V2 获取的客户端真实 IP 格式
  - 通过 SPP 协议传递客户端真实 IP
边缘 DNS
- 概述
- 托管域名 DNS 解析
  - 修改 DNS 服务器
  - 配置域名 DNS 解析记录
  - 批量导入DNS记录
  - DNS 高级配置
  - 解析线路与对应代码枚举
- 接入加速域名
  - 添加加速域名
  - 站点/域名归属权验证
  - 修改 CNAME 解析
  - 验证业务访问
- 别称域名
  - 概述
  - 配置指南
  - 通过别称域名批量接入 SaaS 建站域名
  - 别称域名实现业务的容灾
- 流量调度
  - 流量调度管理
- 源站配置
  - 回源配置
    - 回源超时
    - 配置回源 HTTPS
    - Host Header 重写
    - 回源请求参数设置
    - 回源跟随重定向
    - HTTP/2 回源
    - 分片回源
  - 负载均衡
    - 概述
    - 快速创建负载均衡实例
    - 健康检查策略介绍
    - 查看源站健康状态
    - 相关参考
      - 负载均衡相关概念
      - 请求重试策略介绍
  - 源站组操作指引
  - 相关参考
    - 旧版源站组兼容相关问题
边缘缓存
- 概述
- EdgeOne 缓存规则介绍
  - EdgeOne 内容缓存规则
  - 缓存键（Cache Key）介绍
  - Vary 特性
- 缓存配置
  - 自定义 Cache Key
  - 节点缓存 TTL
  - 状态码缓存 TTL
  - 浏览器缓存 TTL
  - 离线缓存
  - 缓存预刷新
- 清除和预热缓存
  - 清除缓存
  - 预热缓存
- 如何提高 EdgeOne 的缓存命中率
规则引擎
- 概述
- 规则引擎支持的匹配类型与操作
- 规则管理
- 变量

当前内容仅提供英语版本，中文版我们将尽快补充，感谢您的理解。

HTTP/2 回源

Overview
Support EdgeOne nodes to origin-pull using HTTP/2 protocol. HTTP/2 (i.e., HTTP 2.0, Hypertext Transfer Protocol version 2) is the second major version of the HTTP protocol, which can effectively reduce network latency and improve site page loading speed.
Note：
1. When enabled, the origin must support HTTP/2 protocol access.
2. If you need to configure HTTP/2 access, please refer to HTTP/2.
Use Limits
When HTTP/2 origin-pull is enabled and the origin-pull protocol is set to Follow Protocol, if a client sends an HTTP request, the EdgeOne node will perform origin-pull using H2C. However, if the origin server does not support H2C, the origin-pull will fail.
Therefore, if your current origin server does not support H2C and the origin-pull protocol is set to Follow Protocol, to reduce the risk of origin-pull failure, we recommend keeping HTTP/2 origin-pull disabled for the site/domain name.
If your origin-pull protocol is HTTPS, it will not be affected.
Note:
H2C is an unencrypted version of HTTP/2, where C stands for clear text, namely plaintext. HTTP/2 is the second major version of the HTTP protocol, with significant performance improvements including multiplexing of requests and responses, reduced latency, optimized data flow, and header compression. However, the HTTP/2 protocol is typically used over secure HTTPS, requiring encryption by TLS (Transport Layer Security Protocol), while H2C allows the use of HTTP/2 without encryption, enabling performance benefits of HTTP/2 when encryption is not needed or cannot be used. Therefore, EdgeOne uses H2C for origin-pull when HTTP/2 origin-pull is enabled and HTTP is used for origin-pull.
Directions
If you need to enable or disable HTTP/2 origin-pull for the specified domain www.example.com, you can follow the steps below:
1. Log in to the EdgeOne console, click Site List in the left sidebar, and then click the site you want to configure in the site list.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST equals www.example.com.
5. Click the Action, and in the pop-up operation list, select the operation as HTTP/2 origin-pull.Click the switch to enable/disable HTTP/2 origin-pull.
﻿
6. Click Save and Publish to complete the rule configuration.