MINIFY STORAGE UPDATE
MINIFY STORAGE CODE
MINIFY STORAGE DOWNLOAD

But when optimizing SharePoint Framework solutions for performance, you want to allow proxy servers to cache your files.

MINIFY STORAGE DOWNLOAD

There might be cases, when you want users to always download the latest files from your server. When configuring caching settings for files, you can choose if they should be allowed to be cached by proxy servers or not. Many organizations use a proxy server in their network to control network traffic between the internal and public networks. Oh, and it will be also cached by proxy servers. This value will make your file be cached for a year (31.536.000 seconds). In the dialog window, scroll down until you see the CacheControl property and enter as its value public, max-age=31536000. After connecting to your storage account, open your container, click right on the file you want to update, and from the context menu choose Properties. One not mentioned in the docs, is using the Azure Storage Explorer. There are a number of ways in which you can set the value of the CacheControl property on a file in Azure Blob Storage. The CacheControl value can be set directly when uploading a file to Azure Blob Storage, but since the SharePoint Framework gulp task doesn't do it, you need to do it yourself. The value of that header can be set in Azure Blob Storage on each file separately, which gives you granular control of the configuration of your application. You can configure how long browser should cache your files using the Cache-Control response header.

MINIFY STORAGE CODE

This is exactly why, whenever you change the code of your SharePoint Framework solution, the generated bundle has a different hash attached to its file name. And when they do, it's a different file, with a different URL. No matter which one you use, the premise is, that file contents never change.

MINIFY STORAGE UPDATE

If the browser never contacts the web server to check for updates, how do you update your application? There are a number of ways you can go around it. Finally, you decrease the bandwidth usage because fewer files have to be downloaded by the web browser. Then, you decrease the costs for using your web server, because fewer requests are issued and fewer files are served. First of all, your application loads significantly faster, because the web browser doesn't need to download any files from the web server. Using far future expiration on your static files offers you a number of benefits. If done properly, the next time user opens your application, the web browser won't even issue a request to the web server to check if the files have been updated, it will simply load the files that it has already stored on the disk, and that's fast. The first time the user opens your application, the necessary application files are downloaded and stored for a long period of time in the local cache. When building web applications, one of the frequent recommendations is to allow browsers to cache your application files for as long as possible. But did you know that there are settings that you can configure, to change how your files are served? Configure far future expiration Optimize how files from Azure Blob Storage are servedД«y default, Azure blob storage just serves your files the way they have been uploaded. This is the setup for use with SharePoint Framework solutions. Every file in that container gets a URL, such as, that you can use in the browser to load the file. When uploading files to the Azure Blob Storage, you can configure the container to be publicly accessible. Loading files from the Azure Blob Storage

What's more, with a few additional configuration settings, you will ensure that your web parts load quicker and your costs for using the Azure Blob Storage are lower. As it's supported out of the box, this hosting option is extremely convenient to use. And these files can be stored anywhere: from an Apache server under your desk to a specialistic CDN.ДЄs a part of the toolchain, the SharePoint Framework offers you the ability to deploy your web part files to Microsoft Azure Blob Storage. The manifest contains a URL that points to the location where the web part files are stored.

SharePoint Framework solutions consist of two main parts: a package with a manifest, deployed to the App Catalog and scripts and asset files deployed to a web server. However, when building SharePoint Framework solutions, things look differently. That way we would leverage its infrastructure and services. In the past, when building SharePoint customizations, Microsoft recommended us to integrate with SharePoint as closely as possible. Here is what you should do next to ensure that users will load these files as quickly as possible. Using the standard toolchain you can easily deploy your SharePoint Framework files to Microsoft Azure.

Minify storage