shift8

Hello!

Your site is deactivated. Its encouraged to save the api key offline in case this happens, but there are plans to make a simple web based dashboard to be able to do this as well as see bandwidth usage and whatnot.

Thanks!

Hmm.. this is an interesting problem.

We should be adding the “Access-Control-Allow-Origin” header to all proxy requests to your origin site however – but your saying this is a server configuration on your server’s side that is blocking the request?

I like the idea of giving options in the wordpress settings page to select which media you want included in the CDN. Alternatively you can add the CDN url to your access-control-allow-origin headers of your server? If I am misunderstanding please feel free to email the details for me to see the error to [email protected]

I’ll look into the options to select which media either way because I see the benefit in your scenario to having that control. I’ll try my best to push out an update this week or early next week at the latest!

Hello!

We definitely need to automate a mechanism to reset the API key. This would likely involve activating your CDN via an email notification after first registering.

For you I have deactivated your old site. You can register as if its a new site now and it should work. Until the feature can be added, its recommended to keep your api key safe in case it happens again.

Thanks

Thanks for the suggestion!

We are also considering an option to manually set the cache control headers to specify cache expiration times. All of these options would definitely be helpful.

Since this is a free service , we have to grow slowly and steadily in proportion to demand increasing.

Thanks again for the suggestion.

Great question!

I believe static assets are cached for 10 minutes before asking for a new copy. I’d have to double check that but we also send a header asking the browser to locally cache the file for 1 day.

Best practice when dealing with CDNs is to simply increment the version query string for your static CSS/JS file.

If you are are enqueuing your script in your theme’s functions file, you can read this page to learn how to add a version query string to your file : https://developer.ww.wp.xz.cn/reference/functions/wp_enqueue_style/ (there is a $ver variable you can set).

If the CDN sees the query string requested for the file change, it will consider it a new file and fetch it like its a new filename. If for some reason this doesnt happen, let us know!

Ok I’ll look into either option. The honouring of expires headers may be easier because we wouldnt have to build in the extra custom option into our configuration management system but this is definitely a good idea and would give people more options. I’m sure there are other options to provide as well once we go down this route.

Hello Steve,

Are you interested in being able to define custom expires headers for your content? Or would you want us to somehow honour what your server may be setting (i.e. 90day) ?

Thanks

Ah – my mistake. Try one more time? Apologies..