SOLVED
How to fix error when using .woff and .woff2 extensions using IIS instead of Apache?
Hi,
I'm working in AMS on an instance installed by Adobe Engineers on Windows OS.
My customer's receiving since years the following problem when add woff/woff2 fonts to its ACC Web Applications:
Finally I read this KB Article https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-22363.html?lang=en# that should provide a solution....but the solution was only for instances with Apache as web server.
My installation was realized using IIS but no solution was provided for such a web server: in particular, has anyone ideas on how to reproduce in IIS the following steps for apache_neolane.conf?
Thanks a lot,
regards
1 Accepted Solution
Correct answer by
The CORS issue with AC is always interesting.
Personally, I always upload the fonts on a object storage like S3 bucket. They offer good controls on CORS.
Alternatively, You can use the CDN which comes without CORS issues.
I found my way to apply these configurations on a Windows Internet Information Services as follow:
Then I restarted my IIS....but nothing happened!
However, is not very clear in article I mentioned before at this point:
1) what does it mean 'do a clean nlserver'??? I tried with restart, nothing changed. I read
I assumed it was the cleanup option in screenshot, but you can imagine that running such an instruction in Production is scary.
What command has to be executed???
Please help!
Hi dears,
I'm really confused: tracking my network call to page with woff(s) I can read:
It appears that applied configuration is correctly working, but however woff fonts are blocked
Is the KB Article wrong? Or I'm doing some mistake?
Regards
Correct answer by
The CORS issue with AC is always interesting.
Personally, I always upload the fonts on a object storage like S3 bucket. They offer good controls on CORS.
Alternatively, You can use the CDN which comes without CORS issues.
