HTTP2 Delivery of Content FAQ
- Topics:
- Administering
CREATED FOR:
- Admin
Adobe is excited to announce the availability of HTTP/2 delivery of content. When using HTTP/2 you will notice an overall performance increase.
What is HTTP/2?
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/
What are the key benefits of moving to HTTP/2 for content delivery?
Performance improvement varies widely based on factors such as your website’s code, how you are using Dynamic Media, the consumer’s device, screen and location, and so on.
Adobe’s own testing yielded the following results:
- For images, response time improved 7%-28% depending on device and browser. The most notable performance gains were on iOS devices.
- For viewers, load time performance improved up 15%.
The following demonstration illustrates the difference between HTTP/1 versus HTTP/2 loading:
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 Classic license.
-
Use a dedicated domain (that is,
images.company.com
ormycompany.scene7.com
), not a generic Dynamic Media Classic domain (that is,s7d1.scene7.com
,s7d2.scene7.com
, ors7d13.scene7.com
).To find your domains, sign in to your account by way of the Dynamic Media Classic desktop application. Then tap Setup > Application Setup > General Settings. Look for the field labelled 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.
What is the process for enabling HTTP/2 for my Dynamic Media Classic account?
-
You must 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:
-
Primary contact name, email, and phone number.
-
All domains to be transitioned over to HTTP2. That is,
images.company.com
ormycompany.scene7.com
.To find your domains, sign in to your account by way of the Dynamic Media Classic desktop application. Then tap Setup > Application Setup > General Settings. Look for the field labelled Published Server Name.
Click Setup > Application Setup > General Settings. Look for the field labelled Published Server Name.
-
Verify that you use secure HTTPS for rich media requests.
-
Verify you are using the CDN through Adobe and not managed with a direct relationship.
-
Verify you are using a dedicated domain. That is,
images.company.com
ormycompany.scene7.com
, not a generic Dynamic Media domain such ass7d1.scene7.com
,s7d2.scene7.com
,s7d13.scene7.com
.To find your domains, sign in to your account by way of the Dynamic Media Classic desktop application. Then tap Setup > Application Setup > General Settings. Look for the field labelled 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.
- Technical Support adds you to the HTTP/2 customer waitlist based on 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 a successful transition over to HTTP2.
-
When can I expect to be transitioned over to HTTP/2?
Requests are processed in the order that they are received by Technical Support.
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?
You need to download an externsion 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, this is indicated by the extension in the form of a blue Flash symbol, and a header “X-Firefox-Spdy” : “h2”.
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management