In both cases, edge servers write a warning in Akamai's logs. When disabled, edge servers allow such requests, passing the invalid headers to the origin server. Clients receive a 400 Bad Request response. When enabled, edge servers reject requests made with non-RFC-compliant headers that contain invalid characters in the header name or value. Tiered Distribution for API Acceleration.Resource Optimizer Extended Compatibility.Protocol Downgrade (HTTPS Downgrade to Origin).Media Acceleration (QUIC Protocol) Opt-Out.Device Characterization - Forward in Header.Device Characterization - Define Cached Content.Content Characteristics - Streaming Video On-demand.Content Characteristics - Streaming Video Live.Content Characteristics - Dynamic Web Content.Cloud Interconnects for Microsoft Azure.Akamai Provider for Salesforce Commerce Cloud Host Header Control.Akamai Provider for Salesforce Commerce Cloud.Akamai Connector for Salesforce Commerce Cloud.The custom origin (publicly trusted certificate).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |