What should Company D do to prevent the web fonts from being blocked by the browser?

Company D is running their corporate website on Amazon S3 accessed from
http//www.companyd.com. Their marketing team has published new web fonts to a separate
S3 bucket accessed by the S3 endpoint https://s3-us-west1. amazonaws.com/cdfonts.
While testing the new web fonts, Company D recognized the web fonts are being blocked
by the browser. What should Company D do to prevent the web fonts from being blocked by
the browser?

Company D is running their corporate website on Amazon S3 accessed from
http//www.companyd.com. Their marketing team has published new web fonts to a separate
S3 bucket accessed by the S3 endpoint https://s3-us-west1. amazonaws.com/cdfonts.
While testing the new web fonts, Company D recognized the web fonts are being blocked
by the browser. What should Company D do to prevent the web fonts from being blocked by
the browser?

A.
Create a policy on the cdfonts bucket to enable access to everyone

B.
Add the Content-MD5 header to the request for webfonts in the cdfonts bucket from the
website

C.
Configure the cdfonts bucket to allow cross-origin requests by creating a CORS
configuration

D.
Enable versioning on the cdfonts bucket for each web font

Explanation:



Leave a Reply 7

Your email address will not be published. Required fields are marked *


seenagape

seenagape

I have the same idea. C

Simon Liang

Simon Liang

C.

http://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html

Scenario 2: Suppose you want to host a web font from your S3 bucket. Again, browsers require a CORS check (also referred as a preflight check) for loading web fonts, so you would configure the bucket that is hosting the web font to allow any origin to make these requests.