![[]](https://developers.cloudflare.com/_astro/logo.te5VL_aD.svg){kind=link}
- Overview
- Get started
- Cache configuration
- Cache Rules
- Overview
- Create a rule in the dashboard
- Create a rule via API
- Terraform example
- Available settings
- Order and priority
- Examples
- Overview
- Browser Cache TTL
- Bypass Cache on Cookie
- Cache by Device Type
- Cache Deception Armor
- Cache everything for hostnames in a list
- Cache Everything while ignoring query strings
- Cache Level (Cache Everything)
- Cache TTL by status code
- Custom Cache Key
- Edge Cache TTL
- Origin Cache Control
- Query String Sort
- Respect Strong ETags
- Migration from Page Rules
- Edge and Browser Cache TTL
- Always Online
- Cache by status code
- Cache keys
- Caching levels
- Tiered Cache
- Performance review
- Interaction with Cloudflare products
- Changelog
- Glossary
- Home
- /Cache / CDN
- /Troubleshooting
- /edgeResponseBytes and cacheResponseBytes discrepancy
edgeResponseBytes and cacheResponseBytes discrepancy
In HTTP request logs, cacheResponseBytes reflects the uncompressed response size from cache or origin. edgeResponseBytes reflects the final compressed response size sent to the client. Because Cloudflare applies compression (gzip, Brotli) before delivering to the client, edgeResponseBytes is typically smaller than cacheResponseBytes.
On this page
2026 Cloudflare, Inc.
[privacy options]Your privacy choices
[privacy options]Your privacy choices![[privacy options]](https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=26,height=12,format=svg/_astro/privacyoptions.BWXSiJOZ.svg){kind=link}