


Imitation webQQ-<1>Email Verification_PHP Tutorial designed by php+js+mysql
Recently I used php+js+mysql to design a course imitating webQQ, and gained a lot. Now I will summarize the key technologies for everyone to learn and communicate.
Email verification
When the user registers, they will enter their email address in the text box. At this time, the onblur and onchange events of the text box are used to use Ajax refresh-free technology to determine whether the email address entered by the user is legal and whether it conflicts with the registered email address.
Js code
[html]
function checkEmail(Email)
{
var xmlhttp;
if (window.XMLHttpRequest)
{// code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
If(xmlhttp.overrideMimeType)
{//Set MIME category
xmlhttp.overrideMimeType("text/xml");
}
}
else
{// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
var url="checkEmail.php?email="+document.getElementById("email").value; //Go to checkEmail.php for verification
xmlhttp.open("GET",url,true);
xmlhttp.onreadystatechange=function()
{
if (xmlhttp.readyState==4 && xmlhttp.status==200)
{
document.getElementById("error1").innerHTML=xmlhttp.responseText;
}
}
xmlhttp.send(null);
}
function checkEmail(Email)
{
var xmlhttp;
if (window.XMLHttpRequest)
{// code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
If(xmlhttp.overrideMimeType)
{//Set MIME category
xmlhttp.overrideMimeType("text/xml");
}
}
else
{// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
var url="checkEmail.php?email="+document.getElementById("email").value; //Go to checkEmail.php for verification
xmlhttp.open("GET",url,true);
xmlhttp.onreadystatechange=function()
{
if (xmlhttp.readyState==4 && xmlhttp.status==200)
{
Document.getElementById("error1").innerHTML=xmlhttp.responseText;
}
}
xmlhttp.send(null);
}
PHP code
[php]
header('Content-Type:text/html;charset=GB2312'); //Encoding mode setting
include("conn.php");
$email=$_GET["email"];
$len=strlen($email);
if($email==null)
{
echo "*The email cannot be empty!";
}
else
{
If($len>50)
echo "*The email address should not exceed 50 characters!";
}
else
if(eregi("^[_.0-9a-z-]+@([0-9a-z][0-9a-z-]+.)+[a-z]{2,3}$",$ email)) //Use regular expression to verify email in php
$sql="select * from user where email='$email'";
$result = mysql_query($sql);
$num=mysql_num_rows($result);
If($num>0)
echo "*This email address is already in use!";
else
echo "*Email is available!";
else
echo "*This email is not available!";
}
?>
header('Content-Type:text/html;charset=GB2312'); //Encoding mode setting
include("conn.php");
$email=$_GET["email"];
$len=strlen($email);
if($email==null)
{
echo "*The email cannot be empty!";
}
else
{
If($len>50)
{
echo "*The email address should not exceed 50 characters!";
}
else
{
if(eregi("^[_.0-9a-z-]+@([0-9a-z][0-9a-z-]+.)+[a-z]{2,3}$",$ email)) //Use regular expression to verify email in php
{
$sql="select * from user where email='$email'"; //Connect to the database to query to see if the email is used
$result = mysql_query($sql);
$num=mysql_num_rows($result);
If($num>0)
{
echo "*This email address is already in use!";
}
else
{
echo "*Email is available!";
}
}
else
{
echo "*This email address is not available!";
}
}
}
?>
After learning about email verification, I think other verifications should be very simple! (To be continued)
Excerpted from wyzhangchengjin123

Effective methods to prevent session fixed attacks include: 1. Regenerate the session ID after the user logs in; 2. Use a secure session ID generation algorithm; 3. Implement the session timeout mechanism; 4. Encrypt session data using HTTPS. These measures can ensure that the application is indestructible when facing session fixed attacks.

Implementing session-free authentication can be achieved by using JSONWebTokens (JWT), a token-based authentication system where all necessary information is stored in the token without server-side session storage. 1) Use JWT to generate and verify tokens, 2) Ensure that HTTPS is used to prevent tokens from being intercepted, 3) Securely store tokens on the client side, 4) Verify tokens on the server side to prevent tampering, 5) Implement token revocation mechanisms, such as using short-term access tokens and long-term refresh tokens.

The security risks of PHP sessions mainly include session hijacking, session fixation, session prediction and session poisoning. 1. Session hijacking can be prevented by using HTTPS and protecting cookies. 2. Session fixation can be avoided by regenerating the session ID before the user logs in. 3. Session prediction needs to ensure the randomness and unpredictability of session IDs. 4. Session poisoning can be prevented by verifying and filtering session data.

To destroy a PHP session, you need to start the session first, then clear the data and destroy the session file. 1. Use session_start() to start the session. 2. Use session_unset() to clear the session data. 3. Finally, use session_destroy() to destroy the session file to ensure data security and resource release.

How to change the default session saving path of PHP? It can be achieved through the following steps: use session_save_path('/var/www/sessions');session_start(); in PHP scripts to set the session saving path. Set session.save_path="/var/www/sessions" in the php.ini file to change the session saving path globally. Use Memcached or Redis to store session data, such as ini_set('session.save_handler','memcached'); ini_set(

TomodifydatainaPHPsession,startthesessionwithsession_start(),thenuse$_SESSIONtoset,modify,orremovevariables.1)Startthesession.2)Setormodifysessionvariablesusing$_SESSION.3)Removevariableswithunset().4)Clearallvariableswithsession_unset().5)Destroythe

Arrays can be stored in PHP sessions. 1. Start the session and use session_start(). 2. Create an array and store it in $_SESSION. 3. Retrieve the array through $_SESSION. 4. Optimize session data to improve performance.

PHP session garbage collection is triggered through a probability mechanism to clean up expired session data. 1) Set the trigger probability and session life cycle in the configuration file; 2) You can use cron tasks to optimize high-load applications; 3) You need to balance the garbage collection frequency and performance to avoid data loss.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

Notepad++7.3.1
Easy-to-use and free code editor

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

SublimeText3 Mac version
God-level code editing software (SublimeText3)

SublimeText3 English version
Recommended: Win version, supports code prompts!
