Adobe is excited to announce the availability of HTTP/2 delivery of content with the overall benefit of improved performance.
This feature requires that you use the out-of-the-box CDN that is bundled with Adobe Experience Manager Dynamic Media. Any other custom CDN is not supported with this feature.
HTTP/2 improves the way browsers and servers communicate, allowing for faster transfer of information while reducing the amount of processing power that is needed.
The following website describes HTTP/2 and its benefits in a brief and simple manner:
What you must know about HTTP/2
Performance improvement can vary widely. It is based on many factors such as your website’s code, how you use Dynamic Media, the consumer’s device, screen, and location.
Adobe’s own testing yielded the following results:
The following demonstration illustrates the difference between HTTP/1 versus HTTP/2 loading:
To use HTTP/2, you must meet the following requirements:
Use secure HTTPS for your rich media requests.
Use the Adobe-bundled CDN (content delivery network) as part of your Dynamic Media license.
Use a dedicated (non- company-h.assetsadobe#.com) domain.
If you already have a dedicated domain, you can opt in by way of Adobe Customer Support.
If you do not have a dedicated domain, Adobe plans to schedule your transition to HTTP/2 in 2018.
You initiate the request to switch over to HTTP/2; it is not automatically done for you.
To switch over to HTTP/2, initiate an Adobe Customer Support request. See Open a support ticket.
Provide the following information in your support request:
Customer Support adds you to the HTTP/2 customer waitlist based in the order in which requests were submitted.
When Adobe is ready to handle your request, Customer Support contacts you to coordinate the transition and set a target date.
You are notified after completion and can verify successful transition over to HTTP2.
Because the browser does not state this fact, it is necessary to download an extension.
For Firefox and Chrome, there is an extension called “HTTP/2 and SPDY Indicator”. Browsers only support http/2 securely, so it is necessary to call a URL with https to verify. If http/2 is supported, it is indicated by the extension in the form of a blue Flash symbol, and a header “X-Firefox-Spdy” : “h2”.
Requests are processed in the order in which they are received by Customer Support.
There can be a long lead time because the transition to HTTP/2 involves clearing the cache. Therefore, only a few customer transitions can be handled at a time.
The transition to HTTP/2 clears out your cache at the CDN because it involves moving to a new CDN configuration.
The non-cached content directly hits Adobe’s origin servers until the cache is rebuilt again. As such, Adobe plans to handle a few customer transitions at a time so that acceptable performance is maintained when pulling requests from the origin.
Because the browser does not state this fact, it is necessary to download an extension.
For Firefox and Chrome, there is an extension called “HTTP/2 and SPDY Indicator”. Browsers only support http/2 securely, so it is necessary to call a URL with https to verify. If http/2 is supported, it is indicated by the extension in the form of a blue Flash symbol, and a header X-Firefox-Spdy
: h2
.