Akamai BotManager breaks AMP due to script injection
https://www.akamai.com/us/en/products/cloud-security/bot-manager.jsp
Script injected:
This seems similar to earlier issue in Akamai RUM
https://github.com/ampproject/amphtml/issues/12598
@aghassemi @cvazac
Is this something that can resolved at the product level as well by avoiding script injection when pages are identified as AMP
Nothing we can do. Please report this to Akamai. This is likely an oversight/bug on their side and easy for them to fix.
Yes I meant at the Akamai product level - This was tracked as a 3P implementation issue in the previous bug https://github.com/ampproject/amphtml/issues/12598
I will raise this with the BM team and report back ASAP.
Thanks @cvazac!
Closing as off-topic.
Reopening since there's no other place to track this.
/cc @nicjansma
@cvazac Wanted to check if the BM product team has any update on resolving this - I recently ran into this issues again with script being injected on AMP page - see below
Thanks!
I am no longer with Akamai - tapping in @nicjansma in case he's able to speak for the BM team.
Response from the Akamai Bot Manager team: Current Akamai customers can exclude the injection of BMP JavaScript on AMP pages by adding an exclusion path in the injection rules.
Akamai is exploring other options of excluding BMP JavaScript from AMP pages automatically
Sounds good - thanks for the update @nicjansma
How about other 3P scripts for security and/or bot detection (incl. Akamai, BIG-IP etc.), is there a common practice on implementing something like this with amp-script? or submitting a custom component?
We originally compromised on security while switching to AMP, we definitely want to get back to the same standards we were at the time. What would be the suggested approach from the AMP team?
Some documentation or guidance would for sure be helpful.
Most helpful comment
How about other 3P scripts for security and/or bot detection (incl. Akamai, BIG-IP etc.), is there a common practice on implementing something like this with amp-script? or submitting a custom component?
We originally compromised on security while switching to AMP, we definitely want to get back to the same standards we were at the time. What would be the suggested approach from the AMP team?
Some documentation or guidance would for sure be helpful.