Basics
- About the web interface controls
- Always-on DDoS mitigation
- Browser recommendations when using the Fastly web interface
- Content and its delivery
- Fastly POP locations
- Getting started with Fastly
- How caching and CDNs work
- How Fastly's CDN Service works
- HTTP status codes cached by default
- Self-provisioned Fastly services
- Shielding
- Sign up and create your first service
- Working with services
Domains & Origins
Caching
Conditions
Custom VCL
- About VCL Snippets
- Accept-Language header VCL features
- Authenticating before returning a request
- Basic authentication
- Creating location-based tagging
- Custom responses that don't hit origin servers
- Delivering different content to different devices
- Enabling URL token validation
- Guide to VCL
- Isolating header values without regular expressions
- Manipulating the cache key
- IP geolocation variables: Migrating to the new dataset
- Overriding which IP address the geolocation features use
- Response Cookie handling
- Support for the Edge-Control header
- Understanding the different PASS action behaviors
- Uploading custom VCL
- Using dynamic VCL Snippets
- Using edge side includes (ESI)
- Using regular VCL Snippets
- VCL regular expression cheat sheet
Dictionaries
Domains & Origins
- Changing origins based on user location
- Connecting to origins
- Failover configuration
- IPv6 support
- Maintaining separate HTTP and HTTPS requests to origin servers
- Routing assets to different origins
- Setting up redundant origin servers
- Specifying an override host
- Using Fastly with apex domains
- Using Fastly's global POP network
Headers
Image optimization
- About Fastly Image Optimizer
- Automating optimization
- Controlling image quality
- Cropping images
- Fastly Image Optimizer API
- Image optimization VCL boilerplate
- Purging optimized images
- Reorienting images
- Resizing images
- Serving images
- Serving responsive images
- Setting up image optimization
- Trimming images
Load balancing
Performance
Purging
Requests
Responses
Video
Access Control Lists
Securing communications
Security measures
TLS
- Domain validation for TLS certificates
- Enabling HSTS through Fastly
- Enabling TLS 1.3 through Fastly
- Forcing a TLS redirect
- Managing domains on TLS certificates
- Serving HTTPS traffic using certificates you manage
- Serving HTTPS traffic using Fastly-managed certificates
- Setting up free TLS
- TLS key and certificate replacement
- TLS termination
Web Application Firewall
Legacy Web Application Firewall
Logging endpoints
- Log streaming: Amazon S3
- Log streaming: Microsoft Azure Blob Storage
- Log streaming: Cloud Files
- Log streaming: Datadog via syslog
- Log streaming: Datadog
- Log streaming: DigitalOcean Spaces
- Log streaming: Elasticsearch
- Log streaming: FTP
- Log streaming: Google BigQuery
- Log streaming: Google Cloud Pub/Sub
- Log streaming: Google Cloud Storage
- Log streaming: Honeycomb
- Log streaming: HTTPS
- Log streaming: Kafka
- Log streaming: Log Shuttle
- Log streaming: LogDNA
- Log streaming: Logentries
- Log streaming: Loggly
- Log streaming: Heroku's Logplex
- Log streaming: New Relic Logs
- Log streaming: OpenStack
- Log streaming: Papertrail
- Log streaming: Scalyr
- Log streaming: SFTP
- Log streaming: Shape Log Analysis
- Log streaming: Splunk
- Log streaming: Sumo Logic
- Log streaming: Syslog
- Log streaming: Tardigrade
- Log streaming: Wasabi Hot Cloud Storage
Non-Fastly services
Common errors
Debugging techniques
Streaming logs
Account management
- Account lockouts
- Changing your account's company name
- Enabling an IP allowlist for account logins through the web interface
- Enabling and disabling two-factor authentication
- Finding and managing your account info
- Monitoring account activity with the audit log
- Reviewing service activity with the event log
- Using API tokens
Billing
User access and control
Recently viewed Clear
Using GET instead of HEAD for command line caching tests
Last updated August 15, 2018
If you're testing on the command line to determine an object's caching status, then use GET instead of HEAD. For example:
curl -svo /dev/null www.example.com
Default caching behavior of HTTP verbs
By default, the results of GET requests are cached. HEAD requests are not proxied as is, but are handled locally if an object is in cache or a GET is done to the backend to get the object into the cache. Anything other than HEAD or GET requests are proxied and not cached by default.
Back to Top