Chapter 2: Understanding and Avoiding Security Risks
Identifying the Sources of Risk
Minimizing User-Input Risks
Not Revealing Sensitive Information
Summary
Chapter 3: PHP Best Practices
Best Practices for Naming Variables and Functions
Best Practices for Function/Method
Best Practices for Database
Best Practices for User Interface
Best Practices for Documentation
Best Practices for Web Security
Best Practices for Source Configuration Management
Summary
Part II
Chapter 4: Architecture of an Intranet Application
Understanding Intranet Requirements
Building an Intranet Application Framework
Creating a Database Abstraction Class
Creating an Error Handler Class
Creating a Built-In Debugger Class
Creating an Abstract Application Class
Creating a Sample Application
Summary
Chapter 5: Central Authentication System
How the System Works
Creating an Authentication Class
Creating the Central Login Application
Creating the Central Logout Application
Creating the Central Authentication Database
Testing Central Login and Logout
Making Persistent Logins in Web Server Farms
Summary
Chapter 6: Central User Management System
Identifying the Functionality Requirements
Creating a User Class
User Interface Templates
Creating a User Administration Application
Creating a User Password Application
Creating a Forgotten-Password Recovery Application
Summary
Chapter 7: Intranet System
Identifying Functionality Requirements
Designing the Database
Designing and Implementing the Intranet Classes
Setting Up Application Configuration Files
Setting Up the Application Templates
Intranet Home Application
Installing Intranet Applications from the CD- ROM
Testing the Intranet Home Application
Summary
Chapter 8: Intranet Simple Document Publisher
Identifying the Functionality Requirements
The Prerequisites
Designing the Database
The Intranet Document Application Classes
Setting up Application Configuration Files
Setting Up the Application Templates
The Document Publisher Application
Installing Intranet Document Application
Testing Intranet Document Application
Summary
Chapter 9: Intranet Contact Manager
Functionality Requirements
Understanding Prerequisites
The Database
The Intranet Contact Manager Application Classes
The Application Configuration Files
The Application Templates
The Contact Category Manager Application
The Contact Manager Application
Installing Intranet Contract Manager
Testing Contract Manager
Summary
Chapter 10: Intranet Calendar Manager
Identifying Functionality Requirements
Understanding Prerequisites
Designing the Database
The Intranet Calendar Application Event Class
The Application Configuration Files
The Application Templates
The Calendar Manager Application
The Calendar Event Manager Application
Installing the Event Calendar on Your Intranet
Testing the Event Calendar
Summary
Chapter 11: Internet Resource Manager
Functionality Requirements
Understanding the Prerequisites
Designing the Database
Designing and Implementing the Internet Resource Manager Application Classes
Creating Application Configuration Files
Creating Application Templates
Creating a Category Manager Application
Creating a Resource Manager Application
Creating a Resource Tracking Application
Creating a Search Manager Application
Installing an IRM on Your Intranet
Testing IRM
Security Concerns
Summary
Chapter 12: Online Help System
Functionality Requirements
Understanding the Prerequisites
Designing and Implementing the Help Application Classes
Creating Application Configuration Files
Creating Application Templates
Creating the Help Indexing Application
Creating the Help Application
Installing Help Applications
Testing the Help System
Security Considerations
Summary
Part III
Chapter 13: Tell-a-Friend System
Functionality Requirements
Understanding Prerequisites
Designing the Database
Designing and Implementing the Tell- a- Friend Application Classes
Creating Application Configuration Files
Creating Application Templates
Creating the Tell-a-Friend Main Menu Manager Application
Creating a Tell-a-Friend Form Manager Application
Creating a Tell-a-Friend Message Manager Application
Creating a Tell-a-Friend Form Processor Application
Creating a Tell-a-Friend Subscriber Application
Creating a Tell-a-Friend Reporter Application
Installing a Tell-a-Friend System
Testing the Tell-a-Friend System
Security Considerations
Summary
Chapter 14: E-mail Survey System
Functionality Requirements
Architecture of the Survey System
Designing the Database
Designing and Implementing the Survey Classes
Designing and Implementing the Survey Applications
Developing Survey Execution Manager
Setting Up the Central Survey Configuration File
Setting Up the Interface Template Files
Testing the Survey System
Security Considerations
Summary
Chapter 15: E-campaign System
Features of an E-campaign System
Architecting an E-campaign System
Designing an E-campaign Database
Understanding Customer Database Requirements
Designing E-campaign Classes
Creating Common Configuration and Resource Files
Creating Interface Template Files
Creating an E-campaign User Interface Application
Creating a List Manager Application
Creating a URL Manager Application
Creating a Message Manager Application
Creating a Campaign Manager Application
Creating a Campaign Execution Application
Creating a URL Tracking and Redirection Application
Creating an Unsubscription Tracking Application
Creating a Campaign Reporting Application
Testing the E-Campaign System
Security Considerations
Summary
Part IV
Chapter 16: Command-Line PHP Utilities
Working with the Command-Line Interpreter
Building a Simple Reminder Tool
Building a Geo Location Finder Tool for IP
Building a Hard Disk Usage Monitoring Utility
Building a CPU Load Monitoring Utility
Summary
Chapter 17: Apache Virtual Host Maker
Understanding an Apache Virtual Host
Defining Configuration Tasks
Creating a Configuration Script
Developing makesite
Installing makesite on Your System
Testing makesite
Summary
Chapter 18: BIND Domain Manager
Features of makezone
Creating the Configuration File
Understanding makezone
Installing makezone
Testing makezone
Summary
Part V
Chapter 19: Web Forms Manager
Functionality Requirements
Understanding Prerequisites
Designing the Database
Designing and Implementing the Web Forms Manager Application Classes
Creating the Application Configuration Files
Creating Application Templates
Creating the Web Forms Submission Manager Application
Creating the Web Forms Reporter Application
Creating the CSV Data Exporter Application
Installing the Web Forms Manager
Testing the Web Forms Manager
Security Considerations
Summary
Chapter 20: Web Site Tools
Functionality Requirements
Understanding Prerequisites
Designing the Database
Designing and Implementing the Voting Tool Application Class
Creating the Application Configuration Files
Creating the Application Templates
Creating the Vote Application
Installing the Voting Tool
Testing the Voting Tool
Summary
Part VI
Chapter 21: Speeding Up PHP Applications
Benchmarking Your PHP Application
Buffering Your PHP Application Output
Compressing Your PHP Application Output
Caching Your PHP Applications
Summary
Chapter 22: Securing PHP Applications
Controlling Access to Your PHP Applications
Securely Uploading Files
Using Safe Database Access
Recommended php.ini Settings for a Production Environment
Limiting File System Access for PHP Scripts
Running PHP Applications in Safe Mode
Summary
Part VII
Appendix A: What's on the CD-ROM
System Requirements
What's on the CD
Troubleshooting
Appendix B: PHP Primer
Object-Oriented PHP
Appendix C: MySQL Primer
Using MySQL from the Command- Line
Using phpMyAdmin to Manage MySQL Database
Appendix D: Linux Primer
Installing and Configuring Apache 2.0
Installing and Configuring MySQL Server
Installing and Configuring PHP for Apache 2.0
Common File/Directory Commands
Index
Wiley Publishing, Inc. End-User License Agreement
Nội dung
All the error messages that the login.php application generates are taken from the login.errors file shown in Listing 5-4. Listing 5-4: login.errors <?php // Errors for Login application $ERRORS[‘US’][‘MISSING_CODE’] = “No error message found”; $ERRORS[‘US’][‘INVALID_DATA’] = “Invalid data.”; ?> The login.php application displays the login menu using the login.ihtml file, which is shown in Listing 5-5. The $LOGIN_TEMPLATE is set to point to login.ihtml in the login.conf file. Listing 5-5: login.ihtml <html> <head><title>Login</title></head> <body> <! BEGIN mainBlock > <center> <form action=”{SELF_PATH}” method=”POST”> <table border=0 cellpadding=3 cellspacing=0 width=30%> <tr> <td bgcolor=”#cccccc” colspan=2>Login</td> </tr> <tr> <td>Email</td> <td><input type=text name=”email” value=”{USERNAME}” size=30 maxsize=50> </td> </tr> <tr> <td>Password</td> <td><input type=password name=”password” size=30 maxsize=50></td> </tr> <tr> <td align=center colspan=2> 136 Part II: Developing Intranet Solutions 08 549669 ch05.qxd 4/4/03 9:24 AM Page 136 <input type=submit value=”Login”> <input type=reset value=”Reset”> </td> </tr> </table> <input type=hidden name=”url” value=”{REDIRECT_URL}”> </form> <font size=2>Login attempt {ATTEMPT}.</font> </center> <! END mainBlock > </body> </html> The login.ihtml template has a set of template tag variables that are replaced by the login.php application. These template tag variables are explained in Table 5-2. TABLE 5-2 TEMPLATE TAG VARIABLES IN LOGIN TEMPLATE Template Tag Explanation {SELF_PATH} Set as a form action. The login application replaces this with the relative path to the login application itself. This allows the login menu form to be submitted to the login application itself. {USERNAME} Replaced with the username previously entered when the user failed to successfully authenticate the first time. This saves the user from having to type the username again and again when she doesn’t remember the password correctly. This is a user- friendly feature. {REDIRECT_URL} Set to the URL of the application that redirected the user to the login application. {ATTEMPT} Displays the number of login attempts the user has made. When the login attempts exceed the number of attempts set in the $MAX_ATTEMPTS variable in the login.conf file, the user is redirected to the $WARNING_URL page, which is shown in Listing 5-6. Chapter 5: Central Authentication System 137 08 549669 ch05.qxd 4/4/03 9:24 AM Page 137 Listing 5-6: warning.html <html> <head> <title>Invalid Login Attempts</title> </head> <body> <h1>Excessive Invalid Login Attempts</h1> <hr> You have attempted to login too many times. </body> </html> The warning page can be any page. For example, you can set $WARNING_URL to your privacy or network usage policy page to alert the user of your policies on resource usage. Creating the Central Logout Application The central logout application terminates the user session. A flowchart of such an application is shown in Figure 5-6. Figure 5-6: A flowchart for the logout application. Start Stop Yes No Is user already authenticated? Logout the user by terminating the session and redirect the user to the home URL. Show alert message stating that user is not logged in. 138 Part II: Developing Intranet Solutions 08 549669 ch05.qxd 4/4/03 9:24 AM Page 138 The logout application checks to see whether the user is logged in. If the user is not logged in, she is warned of her status. If the user is logged in, her session is ter- minated and the user is redirected to a home URL. Listing 5-7 implements this flow- chart in logout.php. Listing 5-7: logout.php <?php require_once “login.conf”; require_once “login.errors”; /* Session variables must be defined before session_start() method is called */ $count = 0; class loginApp extends PHPApplication { function run() { global $MIN_USERNAME_SIZE, $MIN_PASSWORD_SIZE, $MAX_ATTEMPTS; global $WARNING_URL, $APP_MENU; $email = $this->getRequestField(‘email’); $password = $this->getRequestField(‘password’) ; $url = $this->getRequestField(‘url’); $emailLen = strlen($email); $passwdLen = strlen($password); $this->debug(“Login attempts : “ . $this->getSessionField(‘SESSION_ATTEMPTS’)); if ($this->is_authenticated()) { // return to caller HTTP_REFERRER $this->debug(“User already authenticated.”); $this->debug(“Redirecting to $url.”); $url = (isset($url)) ? $url : $this->getServer(); header(“Location: $url”); Continued Chapter 5: Central Authentication System 139 08 549669 ch05.qxd 4/4/03 9:24 AM Page 139 Listing 5-7 (Continued) } else if (strlen($email) < $MIN_USERNAME_SIZE || strlen($password) < $MIN_PASSWORD_SIZE) { // display the login interface $this->debug(“Invalid Email or password.”); $this->display_login(); $_SESSION[“SESSION_ATTEMPTS”] = $this->getSessionField(“SESSION_ATTEMPTS”) + 1; } else { // Prepare the email with domain name if (!strpos($email, ‘’)) { $hostname = explode(‘.’, $_SERVER[‘SERVER_NAME’]); if (sizeof($hostname) > 1) { $email .= ‘’ . $hostname[1] . ‘.’ . $hostname[2]; } } // authenticate user $this->debug(“Authenticate user: $email with password $password”); if ($this->authenticate($email, $password)) { $this->debug(“User is successfully authenticated.”); $_SESSION[“SESSION_USERNAME”] = $email; $_SESSION[“SESSION_PASSWORD”] = $password; $_SESSION[“SESSION_USER_ID”] = $this->getUID(); if (empty($url)) { $url = $APP_MENU; } // Log user activity $thisUser = new User($this->dbi, $this->getUID()); $thisUser->logActivity(LOGIN); $this->debug(“Location $url”); header(“Location: $url”); 140 Part II: Developing Intranet Solutions 08 549669 ch05.qxd 4/4/03 9:24 AM Page 140 . is redirected to a home URL. Listing 5-7 implements this flow- chart in logout .php. Listing 5-7: logout .php < ?php require_once “login.conf”; require_once “login.errors”; /* Session variables. All the error messages that the login .php application generates are taken from the login.errors file shown in Listing 5-4. Listing 5-4: login.errors < ?php // Errors for Login application $ERRORS[‘US’][‘MISSING_CODE’]. > </body> </html> The login.ihtml template has a set of template tag variables that are replaced by the login .php application. These template tag variables are explained in Table 5-2. TABLE 5-2 TEMPLATE TAG