06 Laravel - Eloquent (DB) Continued, Validation, Cookies and Sessions

Laravel: Eloquent (DB) continued,
Validation, Cookies and Sessions

Web, Mobile and Security
Frédéric Vlummens
Agenda
• Eloquent: recap
• Selecting all records
• Adding a record
• Eloquent use cases
• Selecting a specific record
• Updating a specific record
• Deleting a specific record
• Validation
• Cookies
• Sessions
25/03/2020 Web, Mobile and Security – Laravel: Eloquent (DB) continued, Validation, Cookies and Sessions 2
Eloquent: recap
Eloquent: recap
• Eloquent = ORM (Object-Relational Mapper)

• Database tables have corresponding models, used to interact with tables
• We do not write SQL code ourselves, but let Eloquent generate it for us
• Convention over configuration:
• Table names are plural, corresponding Models singular
• Each table has a PK field called id of type INTEGER AUTO_INCREMENT
• One-to-many relationships are handled in the database by taking singular of table
and suffixing foreign key field with _id
• These are conventions: we do not need to explain Laravel the pluralization rules
or primary keys
• As long as we follow the rules, Eloquent knows what to do
Eloquent: recap
Database table names are pluralized

Primary keys are auto increment integers called id
For 1 to many relationships, the foreign key name consists of the related table name in singular, suffixed by _id
Eloquent: recap
• Selecting all records

using all():
• Adding a specific record

using save():
Eloquent: additional use cases
Eloquent use cases
• Using the find() method, select a record based on its primary key
• Using the save() method, you can also update existing records:
• Using the delete() method, you can delete an existing record:
Validation
Validation
• Validate form input on server-side

• Do not depend on client-side validation only!
• Define rules per parameter
• Rules are combined using the | symbol
• When validation fails, user gets returned to originating view
• $errors variable can be used to display validation errors
Validation
Individual rules per parameter

See https://laravel.com/docs/master/validation
Keys must match name attributes of your form fields
Validation
validate() method returns

an associative array,
containing all validated
values
Validation
• In Blade file:
Only if there are errors…
…loop over them and print

them out
Cookies
HTTP = stateless protocol
• When submitting a form, all previous data is lost

• (Except if we store in database)
• Reason: HTTP is a stateless protocol
• Each request is independent from the subsequent one
HTTP = stateless protocol
• Somehow, we must make sure our webserver code “remembers” us

• Solutions have been developed:
• Cookies
• Sessions
Cookie
• Small text file

• Sent from website (server) and stored by browser (client)
• Upon each subsequent request, the cookie is sent back to the server
• This way, the server “recognizes” the client from previous requests
• Circumvent the statelessness of the HTTP protocol
Cookies in Laravel
• A cookie has a name, value and experiation time

• We put our cookie in the queue. It will be handled by Laravel and sent back to client
via response.
Cookies in Laravel
• Retrieving the cookie:
Cookies: inspecting request – response using Postman
Cookies: what about security?
Visualisation in browser:
• Information is stored locally
• Transmitted with each request
• What about confidential data?
• Some solutions:
• Encryption of cookie value
(=default behavior in Laravel)
• HTTPS
Cookies: overcoming statelessness
Cookies versus local storage
Cookies:
• Key-value pairs (strings)
• Used to obtain state in stateless HTTP world
• Transmitted with each Request – Response
Local storage:
• Key-value pairs (strings)
• Used for local data only
• If you want data in local storage available on server, you need to send it explicitly
( cookies)
Sessions
Overcoming HTTP statelessness
• We now know how to store information in HTTP cookies

• Information is stored on client
• Transmitted to server with each request
• What if we want to store more data?
• Data not to be manipulated at the client side?
• Examples:
• Contents of shopping cart
• Restaurant bookings
• Solution: sessions
Sessions
Sessions
• Each session gets a unique (session) ID

• ID stored, usually in a cookie
• On server side, lots of info can be stored, associated with cookie (e.g. shopping cart)
Sessions in Laravel
• Store something in the session:
• You obtain a reference to the session via $request -> session() method
• Each item has a key (here “my-item”) and value (here contents of $item)
Retrieving something from the session
• Retrieving something from the session
• You obtain a reference to the session via $request -> session() method
• Retrieve item based on its key
Sessions in Laravel
• Keeping list of items (array) in the session
More information?
• https://laravel.com/docs/master/session
Questions?

06 Laravel - Eloquent (DB) Continued, Validation, Cookies and Sessions

Uploaded by

Copyright:

Available Formats

06 Laravel - Eloquent (DB) Continued, Validation, Cookies and Sessions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

06 Laravel - Eloquent (DB) Continued, Validation, Cookies and Sessions

Uploaded by

Copyright:

Available Formats

Laravel: Eloquent (DB) continued,

Validation, Cookies and Sessions

• Eloquent = ORM (Object-Relational Mapper)

Database table names are pluralized

• Selecting all records

• Adding a specific record

• Using the delete() method, you can delete an existing record:

• Validate form input on server-side

Individual rules per parameter

Keys must match name attributes of your form fields

validate() method returns

Only if there are errors…

…loop over them and print

• When submitting a form, all previous data is lost

• Somehow, we must make sure our webserver code “remembers” us

• Small text file

• A cookie has a name, value and experiation time

• Retrieving the cookie:

• We now know how to store information in HTTP cookies

• Each session gets a unique (session) ID

• Store something in the session:

• Retrieving something from the session

• Keeping list of items (array) in the session

You might also like