Am I eligible to switch over to HTTP/2?

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 Technical Support.
If you do not have a dedicated domain, Adobe will schedule your transition to HTTP/2 in 2018.

What is the process for enabling HTTP/2 for my Dynamic Media account?

You must initiate the request to switch over to HTTP/2; it is not automatically done for you.

Initiate a Technical Support request to switch over to HTTP2 (email: s7support@adobe.com)

Provide the following information in your support request:

Primary contact name, email, phone.

All domains to be transitioned over to HTTP2.

Verify you are using secure HTTPS for rich media requests.

Verify you are using the CDN through Adobe and are not managed with a direct relationship.

Verify you are using a dedicated domain. If you use Dynamic Media, then you already are using a dedicated domain.

Technical Support will add you to the HTTP/2 customer waitlist based in the order in which requests were submitted.

When Adobe is ready to handle your request, support will contact you to coordinate the transition and set a target date.

You will be 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, this is indicated by the extension in the form of a blue Flash symbol, and a header "X-Firefox-Spdy" : "h2".

When can I expect to be transitioned over to HTTP/2?

Requests will be processed in the order in which they are received by Technical Support.

註解：

There may 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.

What are the risks with moving to HTTP/2?

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, Adobe plans to handle a few customer transitions at a time so that acceptable performance is maintained when pulling requests from our origin.

How can you verify whether a URL or website is activated with HTTP/2?

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, this is indicated by the extension in the form of a blue Flash symbol, and a header "X-Firefox-Spdy" : "h2".