Book Image

Liferay 6.x Portal Enterprise Intranets Cookbook

Book Image

Liferay 6.x Portal Enterprise Intranets Cookbook

Overview of this book

Table of Contents (19 chapters)
Liferay 6.x Portal Enterprise Intranets Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Turning on the CDN host


In the previous recipe, you learned how to connect with minifying CSS and JS files and reduce the number of requests to the Liferay Portal. The next step in our configuration is reducing requests to the application server where Liferay is. The idea is that some static resources can be served by Apache server or, better, by Squid cache. Delivering static resources through the Apache server or Squid cache instead of the application server improves the response time.

Liferay supports CDN. Wikipedia defines this term as follows:

"A content delivery network or content distribution network (CDN) is a large distributed system of servers deployed in multiple data centers across the Internet. The goal of a CDN is to serve content to end-users with high availability and high performance."

Getting ready…

Our idea is to use CDN domains to serve static resources and cache them in the Squid cache. The most difficult part is the Squid configuration, which caches all the static files...