Forum Discussion
VesaJuvonen
Microsoft
Apr 22, 2017General availability of Office 365 CDN
We are happy to announce general availability for the Office 365 CDN with new great improvements for the CDN asset handling. Please see following blog post from dev.office.com for addition...
Jim Duncan
May 23, 2017Iron Contributor
Hello Vesa,
I notice that the defaul origins for Public vs. Private are quite different.
Our customer is hesitant to use Public CDN for things that live in Master Page Gallery and Style Library but would love to leverage the same functionality under Private CDN.
Current plan is to enable Private CDN (only) and then add to that the origins that would be defaulted for Public.
Questions:
- Is this a viable option?
- Will it work with the Publishing integration automatically?
Thanks!
#MCM #R6 #WUB
VesaJuvonen
Microsoft
May 26, 2017You can absolutely do that. Automatic publishing performance improvements are coming from the private CDN side, so there's no impact for that. Public CDN is more around when you reference the assets directly in your customizations, like with SPFx web parts.
- Jim DuncanMay 26, 2017Iron Contributor
I believe i've done verything correctly:
I've also verified that 'Preview Features' are turned on.
However, none of the URLs are being rewritten. What should I try next?
- Clint LechnerMay 26, 2017Steel ContributorI couldn't get private to work at all but the public worke like a champ first try.
- VesaJuvonenMay 27, 2017
Microsoft
If you enable private and reference image in publishing page from a library, which is enabled as CDN origin, you chould see the URLs being automatically rewritte for the private CDN URLs. This should be working properly cross the SPO currently.
If you however reference that image programatically in your code, it will not be processed automatically. Private CDN is mainly designed currently for increasing performance with publishing sites.