The cache stores both compressed and uncompressed versions of resources, so the data is readily available even for clients without compression support.On subsequent client requests, the system provides the transformed version of the resource from the cache.Minification/compression only occurs once when a resource is requested for the first time (the cache stores the result).To counter this issue, the system uses server-side caching for resource files: The minification and compression process slightly increases the server CPU load and adds a short delay to resource requests. Inline code inserted into the HTML markup of pages is not affected. Note: The reductions only apply to resources stored individually in the file system or database. In cases where the client cannot process compressed data, the system automatically sends the unmodified resource instead. All browsers officially supported by Kentico should be able to correctly decompress files. When a client browser receives a compressed resource, it must first decompress the data. To apply compression, you must also enable minification for resources of the given type. Reduces the size of resources by encoding their data. JavaScript minification does not work on instances running on Microsoft Azure Cloud Services (even if the corresponding setting is enabled).Minified code is difficult to read (for humans) and is therefore unsuitable for debugging.Browsers can immediately handle minified resources without any additional steps. Minified resources behave in exactly the same way as the original. This includes white spaces, line break characters, comments, bookmarks etc. Removes all unnecessary characters from the code that are not required by the browser to correctly process the resource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |