Forum Discussion
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.
- Clint LechnerMay 27, 2017Steel Contributor
Ah, that makes sense. Thanks Vesa.
One more question, or perhaps a feature request.... I don't see the ability to add exceptions. Is that something that might be coming up or do you think it will always be an all or nothing thing?
The reason I ask really is for development. I'd love to say in a perfect world we always have separate dev and prod. However, with client side development, and even with SPFx completely isolating an environment, we end with 1) prod, 2) dev and 3) prod but it's new so we're working on it all the time. The point is, it'd be nice to add an expection so we could have area where we didn't have to worry about the cache timing. For instance, let's say we have a library called /Assets and we put it on the CDN, however, we'd like to have /Assets/code/someproject readily available. It'd be great to have that exception possible...