Adobe is excited to announce the availability of HTTP/2 delivery of content. When using HTTP/2, an overall performance increase is experienced.
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:
https://www.engadget.com/2015/02/24/what-you-need-to-know-about-http-2/
Performance improvement varies widely because it is based on various factors. For example, 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 Classic license.
Use a dedicated domain (that is, images.company.com
or mycompany.scene7.com
), not a generic Dynamic Media domain (that is, s7d1.scene7.com
, s7d2.scene7.com
, or s7d13.scene7.com
).
To find your domains, open the Dynamic Media Classic desktop application, then sign in to your account.
Click Setup > Application Setup > General Settings. Look for the field labeled Published Server Name. If you are currently using a generic Dynamic Media domain, you can request moving over to your own custom domain as part of this transition.
Use the Admin Console to create a support case and request to switch over to HTTP/2; it is not automatically done for you.
Provide the following information in your support case:
images.company.com
or mycompany.scene7.com
.To find your domains, open the Dynamic Media Classic desktop application, then sign in to your account.
Click Setup > Application Setup > General Settings. Look for the field labeled Published Server Name.
images.company.com
or mycompany.scene7.com
, not a generic Dynamic Media domain such as s7d1.scene7.com
, s7d2.scene7.com
, s7d13.scene7.com
.To find your domains, Open the Dynamic Media Classic desktop application, then sign in to your account.
Click Setup > Application Setup > General Settings. Look for the field labeled Published Server Name. If you are currently using a generic Dynamic Media domain, you can request moving over to your own custom domain as part of this transition.
Requests are processed in the order that they are received by Technical Support.
There is 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. Because of this action, Adobe plans to handle a few customer transitions at a time. This method ensures that acceptable performance is maintained when pulling requests from the origin.
Download an extension to use with your Web browser. 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”.