DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
EXT: zooom Akamai Handler¶
Author: | Christopher |
---|---|
Created: | 2010-12-18T19:57:23 |
Changed: | 2014-07-01T16:20:39 |
Classification: | zoat_akamai |
Author: | Hannes Maier |
Email: | hannes.maier@zooom.at |
Language: | en |
Akamai CCU / ECCU Purge¶
Extension Key: zoat_akamai
Language: en
Version: 2.2
Keywords:
Copyright 2013, Hannes Maier, <hannes.maier@zooom.at>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.org
Table of Contents¶
`zooom Akamai Handler 1 <#__RefHeading__5708_1738894311>`_
`Introduction 3 <#__RefHeading__5710_1738894311>`_
`Users manual 4 <#__RefHeading__467_413120346>`_
`Configuration 5 <#__RefHeading__31515_818911409>`_
`Known problems 6 <#__RefHeading__31525_818911409>`_
`To-Do list 7 <#__RefHeading__477_413120346>`_
`ChangeLog 8 <#__RefHeading__31623_818911409>`_
Introduction¶
What does it do?¶
- CCU REST and ECCU SOAP Akamai
- Hooks clearCachePostProc and clearPageCacheEval collect purge information
- CCU/ECCU statements collected in a table
- Scheduler Task to periodical send CCU/ECCU statements to Akamai
- Menu Item added to purge by CP-Code
- tt_content / pages and tt_news changes in Version 1.
- Feel free to add your own plugins / statements
- Akamai Dokus (only available with valid logins):
Screenshots¶
Menu item for CCU by CP-Code (use with caution)
Users manual¶
Hooks generate URLs (special page type) which are stored in the database.
On a regular basis these URLs are read with CURL (to have full access to th TSFE, typolink, RealUrl, …)
Via the special page type you land in /service/class.tx_zoatakamai_service.php where the params from the URL are parsed and evaluated which statements should be sent to Akamai.
Here you can add you own classes to generate ARLs (for CCU), ...
Configuration¶
Configuration is done at plugin installation.
Don't forget to add the static extension template!
Page 1 should be the rootpage
Extension setup:
- CP Code: provided by Akamai / business sponsor
- Host Header: provided by Akamai / business sponsor
- Domain: production / staging
- API Username: provided by Akamai / business sponsor
- API Password: provided by Akamai / business sponsor
- API action: remove / invalidate
- Notification Email address (only for ECCU SOAP)
Page Setup:
- add the static extension template
- for plugin-data setup TCEMAIN.clearCacheCmd in the sys-Folder
Known problems --------------
None
To-Do list¶
- Maybe think much simpler and send only ECCU on default and custom file extensions (but this way the whole project would be purged – and it takes longer...)
- add “default file extension” to configuration
- Bugfixing :)
ChangeLog¶
Create a file "ChangeLog" (see e.g. the extension "cal") to inform about changes or use this section to document all the changes through the versions.
Alternatively to using the following list: ChangeLog online (Forge gives the possibility to create a Roadmap very easily; change this link to point to YOUR extension)
2.2¶
Version
2.2
Changes
Akamai CCU changed to REST API
2.1.0 - 2.1.2¶
Version
2.1.0 - 2.1.2
Changes
Bugfixes
2.0.0¶
Version
2.0.0
Changes
First version