Sometimes the page.aspx part is not displayed in the URL and the web server returns a particular page to you by default based on the path. This the file you want the web server to actually return to you - the /path/subpath are literally folders on the server you are connecting to - just like the folders on your laptop.

/path/subpath/page.aspx - this is the URI, Uniform Resource Identifier - or sometimes called the path.

Your browser translates the domain name into the proper IP address using DNS - the Domain Naming System - behind the scenes. The internet does not understand text like this, it only understands IP addresses like 192.168.1.24.

- this is the domain name or in-lay man’s terms the name of the actual computer you are connecting to.

If you want to use plain unencrypted http - you just start with

- This is the Protocol that your browser is using, nowadays most browsers default to https - the encrypted version of http - some don’t even display it by default.

Unsurprisingly, the primary way your browser constructs the request to the server is using the URL. The server says: send me a request that is formatted like x, y, z and I’ll process your request the way you expect and send you something that you can understand and display properly on the monitor. In other words, your browser and the server hosting the web page you are connecting to have a “contract” in how they both should communicate with each other. To start, it’s important to remember that the P in HTTP stands for Protocol - which can be defined as a set of rules governing the exchange or transmission of data between devices. Today we’re going to take a deep dive into AWS WAF and how its rule engine works under the hood.

Awsmanagedrulessqliruleset