Gain insights into modern PHP by delving into POST requests, forms, sessions, and redirects to build a CRUD app with authentication, focusing on pure PHP without frameworks.

Learn PHP Without a Framework by Matthias Noback.png

php-setup.tar.gz

php-job

php-favi

php-pub

php-public

php-error

php-mult

php-tests

PHP for the Web is a terrific introduction on how to use modern PHP effectively. While there is a lot of material out there about building applications with PHP, most of them focus on using a framework like Laravel or Symfony. By working with pure PHP, you will be able to focus on the core ideas instead of how a particular framework implements them.

In this course, you will learn how to use multiple web technologies like POST requests, forms, sessions, and redirects to build a CRUD application with an authentication system.

By the end, you will have all the ingredients at your disposal to go out and build stunning, dynamic PHP web applications.

PHP for the Web: Learn PHP without a Framework

## Set-Cookie header and Cookie header
Personally, I've had a lot of trouble understanding cookies and how to use them correctly.
That's because I didn't realize they were *headers*.
When you call `setcookie()`, the result is not some magic cookie (whatever that is), but a `Set-Cookie` response header.
Only when the browser has received the response from the server, it will process the `Set-Cookie` headers of the response and keep the provided values in its own storage facility.
The next time it makes a request to your server, it will look in that same storage facility for any cookies that should be sent to the server as a `Cookie` header on the request.
The following diagram illustrates this process of setting a cookie and getting that cookie in the next request:


# Set-Cookie header and Cookie header
Personally, I've had a lot of trouble understanding cookies and how to use them correctly.
That's because I didn't realize they were *headers*.
When you call `setcookie()`, the result is not some magic cookie (whatever that is), but a `Set-Cookie` response header.
Only when the browser has received the response from the server, it will process the `Set-Cookie` headers of the response and keep the provided values in its own storage facility.
The next time it makes a request to your server, it will look in that same storage facility for any cookies that should be sent to the server as a `Cookie` header on the request.
The following diagram illustrates this process of setting a cookie and getting that cookie in the next request:


Getting Started

Serving Resources

Serving PHP Scripts

Forms

Cookies

Sessions

Authentication

PHP Project Structure

CRUD Part 1: Create

CRUD Part 2: The Rest

File Uploads

Error Handling

Automated Testing

Conclusion

Cookies Are Headers

Set-Cookie header and Cookie header