DocumentationExperience Cloud KCS

Supported HTTP protocol versions in AEMaaCS

Last update: August 31, 2026

In Adobe Experience Manager as a Cloud Service (AEMaaCS), this article explains which HTTP protocol versions are supported and how to verify protocol usage through access logs. It also explains when it is appropriate to remove application logic that depends on HTTP/1.0.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEM as a Cloud Service)

Issue/Symptoms

  • Uncertainty about which HTTP protocol versions are supported in AEM as a Cloud Service.
  • Need to determine whether application logic that depends on legacy HTTP protocols should remain in use.
  • Need to verify the HTTP protocol versions used by AEM as a Cloud Service components.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Review the access logs from your AEMaaCS environment to confirm the HTTP protocol versions in use.
  2. Review Dispatcher access logs. For Apache HTTPD (Dispatcher) access logs, refer to the Apache HTTPD web server access log documentation.
  3. Review AEM Publish access logs. For AEM Publish access logs, refer to the AEM HTTP access logging documentation.
  4. Examine log entries for the proto_version field or the HTTP request line to verify the protocol version. For example: GET /system/probes/health?aemService=... HTTP/1.1" 200 27 "-" "Envoy/HC" proto_version: 1.1
  5. If your application logic depends on HTTP/1.0 compatibility, it is safe to remove this logic for AEMaaCS environments.
  6. To verify, check recent access logs for protocol version fields and confirm that only HTTP/1.1 (or HTTP/2 for CDN communication) is present.
recommendation-more-help
experience-cloud-kcs-help-kbarticles