A reverse proxy server acts as an intermediary for requests from clients seeking resources from other servers. It provides an additional layer of abstraction and control to ensure the …
Read More
Caching, when properly configured, can instruct user's browsers to locally store and reuse previously fetched resources. This ensures faster page loads for returning users, as their browsers can retrieve …
Read More
It is crucial to optimize page load time as it helps with user experience (UX) and conversion. It's also important for SEO with Google now officially using Core Web …
Read More
Websites are typically hosted on a URL that starts with or without www. The choice could be personal, though sometimes are required. Certain CDN, for example, requires a website …
Read More
HTTPS provides encrypted traffic with the use of SSL or TLS. As websites are moving away from HTTP to HTTPS, it's generally a good idea to automatically redirect visitors …
Read More
Apache Access Log records incoming HTTP requests to the server, and CustomLog directive defines what is kept in the log. The following is an example HTTP request, CustomLog directive, …
Read More
Apache, by default, will serve files to the users as fast as the bandwidth or TCP/IP allows. In an environment where you are hosting files for download, and you …
Read More
HTTP/2 is a significant improvement over HTTP/1.1, especially in the speed department. Apache supports HTTP/2 though it's disabled by default.
You can enable HTTP/2 for …
Read More
HSTS or HTTP Strict Transport Security provides an extra layer of security for HTTPS (SSL / TLS) traffic by preventing HTTPS connections from being downgraded to HTTP, which is …
Read More
Apache‘s reverse proxy is an act of an Apache webserver providing content from other webserver transparently. This is useful in many instances such as caching and mirroring, but it’s mostly used to serve websites that are hosted behind NAT or a firewall. A reverse proxy server routes connection addressed to the internal server, and the client sees the reverse proxy server itself as the origin server.
For example, Apache can be configured to serve URL‘s such as http://www.example.com/webapp to actually get the content from http://192.168.0.10/myapp, which is hosted from an internal network. This happens transparently and the user initially requesting http://www.example.com/webapp need not to be aware of what happens in the background.
