Our first lesson for web exploitation, will be web fundamentals

L1 • What is HTTP/HTTPS (First thing you should learn)

Http = Hypertext Transfer protocol it is basically the protocol browsers use to communicate with web servers.

Https = Http but with TLS encryption it basically encrypts the connection between your browser and the server ensuring more security.


• Why HTTPS is more secure than HTTP

Http: isn't good security because traffic can be read or modified

Https: is good due to encryption preventing that and the fact it lets the server prove itself using TLS certificate.

Obviously I can't just immediately teach you guys how to exploit a website

You must first know how a website works before you can exploit one.

L2 • HTTP Requests vs Responses

Request = What your browser sends to a web server when it wants something, like opening a webpage or logging into an account.

Response = What the server sends back after receiving the request.

• Example

Request:
"GET /login HTTP/1.1"

This means the browser is asking the server for the "/login" page using the GET method.

Response:
"HTTP/1.1 200 OK"

This means the server successfully received the request and is sending the requested page back.

Basically, request = what you send and response = what you get back.

L3 • HTTP Methods

HTTP methods are basically commands that tell the server what you want to do with a resource.

GET: Used to request or retrieve something from the server.

POST: Used to send data to the server, like when logging into an account or submitting a form.

PUT: Used to update or replace existing data.

DELETE: Used to delete something from the server.

• Example

"GET /profile"

This is asking the server to return the profile page.

"POST /login"

This is sending login information to the server.

Basically, GET = get data, POST = send data, PUT = update data, DELETE = delete data.

Doing 3 lessons at night, 3 lessons at day.

Alr servers back
discord.gg/believing

Hold thy tongue good sir for every word thou utterest doth diminish the reputation of mankind

L4 • HTTP Headers

HTTP headers = Extra information sent with HTTP requests and responses. They tell the browser or server things about the request or response.

• Common Request Headers

User-Agent = Tells the server what browser or device is making the request.

Cookie = Sends stored cookies to the server.

Content-Type = Tells the server what type of data is being sent.

• Example

Request:
"GET /profile HTTP/1.1
Host: example.com
User-Agent: Chrome
Cookie: session=abc123"

This tells the server which page we're requesting, what client is making the request, and sends the user's session cookie.

Basically, HTTP headers are extra information that helps the browser and server understand how to handle the request.

L5 • HTTP Status Codes

HTTP status codes = Numbers the server sends back to tell you what happened with your request.

• Common Status Codes

200 = Request was successful

301 = Resource was permanently moved

302 = Resource was temporarily moved

400 = Bad request

401 = Authentication is required

403 = Server understood the request but refuses access

404 = Resource wasn't found

500 = Server encountered an error

• Example

Request:
"GET /login HTTP/1.1"

Response:
"HTTP/1.1 404 Not Found"

This means the server received the request but couldn't find the "/login" resource.

Basically, status codes tell you whether a request worked, failed, or was redirected.

L6 • HTTP Request & Response Bodies

Body = The actual data being sent to or received from a web server.

Request body = Data sent from the browser to the server, usually when submitting information.

Response body = Data sent from the server back to the browser.

• Example

Request:

"POST /login HTTP/1.1
Content-Type: application/json

{"username":"alex","password":"1234"}"

The body contains the username and password being sent to the server.

Response:

"HTTP/1.1 200 OK
Content-Type: application/json

{"message":"Login successful"}"

The body contains the data the server sends back.

Basically, the body is where the actual data being sent between the browser and server can be stored.