URL Handling (Wrapping my head around Akamai) [#2632154]

I'm still trying to wrap my head around Akamai on a new project we're working on. Wondering if this module can be any help.

We currently have our origin set at origin.site.com with the final akamai cache url as site.com as one would expect. My question is how you handle the normal day to day events on a drupal site while its under full cache from akamai. For example

1) When a user visits the site all urls (including canonicals point to origin.site.com. This means when someone shares and article or views soure they're seeing the origin URL. Not good. Can we hide this away somehow or does this module provide tools for those basic configs

2) Drupal redirects within the app itself will redirect to origin urls and not site.com. Would we need to set the base URL to site.com or can the module provide this type of config?

What im basically looking for are how most people have set up their systems with Akamai and move around this seemingly obvious issues.

Comment	File	Size	Author
#2	Selection_763.png	84.16 KB	elijah lynn

Comments

Comment #1

10 December 2015 at 01:56

Media Crumb created an issue. See original summary.

Comment #2

elijah lynn

Portland, Oregon

commented 5 February 2016 at 21:19

Issue summary:

View changes

Status	File	Size
new	Selection_763.png	84.16 KB

Nobody should ever see your origin URL. The origin URL should only be used in the Akamai configuration or as a way to debug something.

origin.example.com is what you configure your webserver to look for. Then configure your DNS for www.example.com to point to Akamai, something like *.edgesuite.com. Akamai will give this to you when you configure a hostname on the Akamai 'property'. So you have your DNS configured for example.com -> edgesuite. Then you configure Akamai to use origin.example.com for the hostname example.com. You then need to setup DNS A record to point origin.example.com to xx.xx.xx.xx IP address. Then configure your webserver to accept both domains.

Here is a screenshot of what it looks like in the control panel. The different hostnames are for load.*, qa.*, dev.* etc. We have rules to just point to different origins for different hostnames.