Forum Discussion
General availability of Office 365 CDN
Is there any guidance or recommendations around the type of new Site Collection and or library we should be creating for our CDN Origins. Do Public and Private CDN origins need to be on separate site collections, say to accomodate the URL rewriting?
e.g. Team Site - SharePoint Online configuration and Asset Library
# private Add-SPOTenantCdnOrigin -CdnType Private /sites/cdn/ec-cdn #public Add-SPOTenantCdnOrigin -CdnType Public /sites/cdn/cdn.
Added to the above, I am working with a client that has multple team sites with each site having a /clientnameImages library which they use to surface event pics on to their respective home sites.
Add-SPOTenantCdnOrigin -CdnType Private */ClientNameImages Add-SPOTenantCdnOrigin : A positional parameter cannot be found that accepts argument *ClientNameImages. At line:1 char:1 + Add-SPOTenantCdnOrigin -CdnType Private */ClientNameImages
Do I need relocate each teamname/clientnameImages under /SiteAssets?
You can define any library or folder as a CDN origin. You can use wildcard mapping or relative URL for the origins. In your specific sample, you have a small bug around hte Add-SPOTenantCdnOrigin cmdlet execution. In your case, it should be looking as follows.
Add-SPOTenantCdnOrigin -CdnType Private -OriginUrl "*/ClientNameImages"
- Daniel WesterdaleMay 26, 2017Iron Contributor
Vesa
Thanks. Interesting, as I had tried single quotes and got the error . Double quotes accepted . Thanks
BTW This issue I am trying to fix we have seen on a few team sites using the new Origin