Expand my Community achievements bar.

Adobe Campaign User Groups are live now. Join our Adobe Campaign User Groups and connect with your local leaders!
SOLVED

How to fix error when using .woff and .woff2 extensions using IIS instead of Apache?

Avatar

Level 3

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:

mirkomanga_0-1707321549118.png

 

 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?

mirkomanga_0-1707313830751.png

Thanks a lot, 
regards


 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

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.

https://cdnjs.com/libraries/font-awesome


     Manoj
     Find me on LinkedIn

View solution in original post

5 Replies

Avatar

Level 3

I found my way to apply these configurations on a Windows Internet Information Services as follow:

mirkomanga_0-1707315433381.png

Then I restarted my IIS....but nothing happened!
However, is not very clear in article I mentioned before at this point:

mirkomanga_0-1707315969497.png

1) what does it mean 'do a clean nlserver'??? I tried with restart, nothing changed. I read 

mirkomanga_1-1707316173511.png

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!

 

Avatar

Level 3

Hi dears,

I'm really confused: tracking my network call to page with woff(s) I can read:

mirkomanga_0-1707321141849.png

It appears that applied configuration is correctly working, but however woff fonts are blocked

mirkomanga_2-1707321281031.png

Is the KB Article wrong? Or I'm doing some mistake?
Regards

Avatar

Correct answer by
Community Advisor

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.

https://cdnjs.com/libraries/font-awesome


     Manoj
     Find me on LinkedIn

Avatar

Level 3

Hi @_Manoj_Kumar_ 
really thanks for the idea I'll check ASAP and I'll let you know if workaround was successful!
Regards

Avatar

Level 3

Hi @_Manoj_Kumar_ 

it works and it appears to be safe for my customer's security policies.
Really thanks and regards