Best Practice Guidelines for Anti-Shake and Anti-Duplicate Submissions in PHP

Best practice guide for anti-shaking and anti-duplicate submission in PHP

Introduction:
With the continuous development of the Internet, user interaction has become more and more frequently. In web applications, users may encounter two common problems when submitting forms: anti-shaking and preventing repeated submissions. This article will introduce best practices in PHP to solve these two problems and provide specific code examples.

1. The concept and principle of anti-shake:
When a user frequently triggers an action within a period of time, such as clicking a button or changing the content of an input box, in order to reduce unnecessary requests and To improve user experience, we can perform anti-shake processing on movements.
The principle of anti-shake is: within a specific time delay, if the action is triggered again, the delay time will be retimed; if the action is not triggered again, the corresponding operation will be performed.

2. How to implement anti-shake:
The following is a simple function to implement anti-shake:

function debounce(callable $callback, $delay) {
    $timer = null;
    
    return function() use ($callback, $delay, &$timer) {
        if ($timer) {
            clearTimeout($timer);
        }
        
        $timer = setTimeout(function() use ($callback) {
            call_user_func_array($callback, func_get_args());
        }, $delay);
    }
}

The above function accepts a callback function and delay time as parameters. When this function is called, a new function is returned. The new function will no longer execute the callback function within the delay time after the user triggers the action. Only when the delay time is reached, the callback function is executed.

3. The concept and principle of preventing repeated submissions:
When a user clicks the submit button multiple times on an operation, we need to ensure that only the first submission is valid, and subsequent repeated submissions are should be ignored. In order to achieve this requirement, we can use Token mechanism and redirection.

The principle of the Token mechanism is to generate a unique Token in the form and store the Token in the Session. When the user submits the form, the server needs to verify the validity of the Token. If the Token is invalid, it means that the submission is a duplicate submission and should be ignored.

4. How to prevent repeated submissions:
The following is a code example to prevent repeated submissions based on the Token mechanism and redirection:

function generateToken() {
    $token = sha1(uniqid(rand(), true)); // 生成一个唯一的Token
    $_SESSION['token'] = $token; // 将Token存储于Session中
    
    return $token;
}

function isValidToken($token) {
    if (empty($_SESSION['token']) || $_SESSION['token'] !== $token) {
        return false; // Token无效
    }
    
    unset($_SESSION['token']);
    return true; // Token有效
}

if ($_SERVER['REQUEST_METHOD'] === 'POST') {
    $token = isset($_GET['token']) ? $_GET['token'] : null;
    
    if (!isValidToken($token)) {
        header('Location: /'); // 重定向到首页或其他页面
        exit;
    }
    
    // 处理表单提交的逻辑
    // ...
}

In the form, we need to add a Hidden domain to store the generated Token:

<form action="/submit" method="post">
    <input type="hidden" name="token" value="<?php echo generateToken(); ?>">
    <!-- 其他表单字段 -->
    <!-- 提交按钮 -->
</form>

In the above code, a unique Token is first generated through the generateToken function and the Token is stored in the Session. When the user submits the form, the server verifies the validity of the token through the isValidToken function. If the Token is invalid, the user will be redirected to the homepage or other pages to ignore subsequent repeated submissions.

Conclusion:
Through the best practices of anti-shaking and preventing repeated submissions, we can effectively improve the performance and user experience of web applications. In practical applications, appropriate anti-shake and repeated submission solutions can be selected according to specific needs.

The above is the detailed content of Best Practice Guidelines for Anti-Shake and Anti-Duplicate Submissions in PHP. For more information, please follow other related articles on the PHP Chinese website!