-
StackOverflow Slack Community 2 Featured Tutorial 2 Contribution Guidelines 2 Contribution Style Guide 2 About Laravel 2 Main Features 2 MVC 2 Blade Templating Engine 3 Routing & Middleware 3 Artisan ORM 3 Event Handling 3 Versions 3 Examples 4 Welcome to Laravel tag documentation! 4 Starter Guide 4 Getting Started 4 Laravel Views 5 Chapter 2: Artisan 6 Syntax 6 Parameters 6 Examples 8 Introduction Relationship Types 77 One to Many 77 One to One 78 How to associate between two models (example: User and Phone model) 78 Explanation 79 Many to Many 79 Polymorphic 80 Many To Many 82 Chapter 23:
0 码力 |
216 页 |
1.58 MB
| 1 年前 3
-
Introduction 2. Prologue i. Release Notes i. Laravel 5.0 ii. Laravel 4.2 iii. Laravel 4.1 ii. Upgrade Guide i. Upgrading To 5.0 From 4.2 ii. Upgrading To 4.2 From 4.1 iii. Upgrading To 4.1.29 From <= 4.1 1.x iv. Upgrading To 4.1.26 From <= 4.1.25 v. Upgrading To 4.1 From 4.0 iii. Contribution Guide i. Bug Reports ii. Core Development Discussion iii. Which Branch? iv. Security Vulnerabilities v Services i. Authentication i. Introduction ii. Authenticating Users iii. Retrieving The Authenticated User iv. Protecting Routes v. HTTP Basic Authentication vi. Password Reminders & Reset vii. Social
0 码力 |
242 页 |
1.44 MB
| 1 年前 3
-
database 6. How to use migrations to create and modify the database schema 7. Using forms to accept user input and store it into the database 8. Adding a better layout 9. Adding the form at the bottom interesting stuff in Blade templates: insert data, add conditionals, do loops, display something if the user is authenticated or not, or show different information depending on the environment variables (e development), and much more. Here’s a 101 on Blade (for more I highly recommend the official Blade guide). In the route definition, you can pass data to a Blade template: Route::get('/test', function ()
0 码力 |
111 页 |
14.25 MB
| 1 年前 3
-
DUMPFILE, … Exemples10 SELECT titre, num FROM livres WHERE num=2 UNION SELECT login, password FROM user INTO DUMPFILE 'www/exploit.txt' Eviter les injections SQL • N’accepter que des caractères valides acteurs : – User Agent : Humain / Navigateur – Relying Party : Serveur (service auquel on veut s’authentifier) – Authenticator : Clef USB / Smartphone / OS + biométrie • Communication : – User Agent <=> <=> Authenticator : CTAP / U2F – User Agent <=> Relying Party : API JS WebAuthn28 7 Figure 2: Architecture 8 Figure 3: Reg 9 Passkeys : Acteurs29 Passkeys : Enregistrement30 Passkeys : Authentification31
0 码力 |
12 页 |
474.37 KB
| 1 年前 3
-
9) – Connexion, GET, réponse, fermeture • HTTP 1.0 (1996) – Entêtes de requête (Host, Referer, User-Agent, …) et réponse (Content-Type, Set- Cookie, Location, …) • HTTP 1.1 (1997) – Nouveaux entêtes sûres Echanges HTTP • Requête GET / HTTP/1.1[CRLF] Host: www.cff.ch[CRLF] Connection: close[CRLF] User-Agent: Opera/9.20 (Windows NT 6.0; U; en)[CRLF] Accept-Encoding: gzip[CRLF] Accept-Charset: ISO-8859-1