Implement it

[trieloff]

No description provided.

[github-actions]

This PR will trigger a minor release when merged.

[codecov]

Codecov Report

Merging #2 into main will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #2   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            6        38   +32     
=========================================
+ Hits             6        38   +32     

Impacted Files	Coverage Δ
src/index.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update af2734c...f0682e9. Read the comment docs.

[trieloff]

Try https://adobeioruntime.net/api/v1/web/helix/helix-services/purge@ci?host=theblog--adobe.hlx.page&xfh=blog.adobe.com&path=/en/2020/08/14/6-ways-ta-adapt-advance-your-business-during-pandemic.html

[dominique-pfister]

xfh === X-Forwarded-Host ?

[rofe]

Nice! But...

Try https://adobeioruntime.net/api/v1/web/helix/helix-services/purge@ci?host=theblog--adobe.hlx.page&xfh=blog.adobe.com&path=/en/2020/08/14/6-ways-ta-adapt-advance-your-business-during-pandemic.html

... obviously in the case of theblog it's not so simple, because the paths differ between inner and outer CDN... it would be cool if instead of the path parameter, one could alternatively specify a surrogate key. This way we could also use this service to bust all cached index json segments at once.

We could then create a "Purge cache" bookmarklet, similar to the "Preview" one, which calculates the surrogate key from the URL of the source document.

[trieloff]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• v1.0.0
• GitHub release

Your semantic-release bot 📦🚀