Home  >  Article  >  Backend Development  >  Solution to the problem of missing return data after php form submission error, php form_PHP tutorial

Solution to the problem of missing return data after php form submission error, php form_PHP tutorial

WBOY
WBOYOriginal
2016-07-12 08:55:421199browse

Solution to the problem of returned data disappearing after php form submission error, php form

This article introduces to programmers the solution to the problem of returned data disappearing after php form submission error, Interested programmers can refer to it.

What should I do if the returned data disappears after the form is submitted incorrectly? Today we will analyze and solve this problem.

Condition Overview:

A problem encountered when filling in form information and submitting it is that after the user fills in and submits the form, the program determines that it does not meet the requirements and returns. After returning, the previously filled form information will be cleared. It doesn't matter if the amount of information filled in is small, but if the amount of information filled in is relatively large, it will directly affect the good mood of the person filling in the information. Therefore, solving the problem of the filled-in content disappearing after a form submission error returns is an urgent issue to improve user experience.

For this kind of problem, we have summarized the following situations:

(1) The page uses the session_start function. One feature of this function is that it will force the current page not to be refreshed. The solution is to add the following code after this function:

<span>header</span>("Cache-control:private");<span>//</span><span>注意在本行之前你的PHP程序不能有任何输出 </span>

There are several other solutions by adding

before session_start
<span>session_cache_limiter</span>('nocache'); <span>//</span><span>清空表单 </span>
<span>session_cache_limiter</span>('private'); <span>//</span><span>不清空表单,只在session生效期间 </span>
<span>session_cache_limiter</span>('public'); <span>//</span><span>不清空表单,如同没使用session一般 </span>

The above setting of session will cause the seesion to be cached, which will cause the problem that the session information cannot be updated when you apply it to the session. For this reason, this article proposes several other solutions below.

(2) Use the Header method to set the message header Cache-control and add the following code to the page:

<span>header</span>('Cache-control: private, must-revalidate');  <span>//</span><span>支持页面回跳,注意本行之前不能有任何输出</span>

(3) Use the session_cache_limiter method and add the following code to the page:

<span>session_cache_limiter</span>('private, must-revalidate'); <span>//</span><span>注意要写在session_start方法之前 </span>

The following is a supplementary explanation of the Cache-Control message header field:

Cache-Control specifies the caching mechanism that requests and responses follow. Setting Cache-Control in a request message or response message does not modify the caching process during the processing of another message. The caching instructions in the request include no-cache, no-store, max-age, max-stale, min-fresh, only-if-cached, and the instructions in the response message include public, private, no-cache, no-store, no-transform, must-revalidate, proxy-revalidate, max-age. The meaning of the instructions in each message is as follows:

Public: indicates that the response can be cached by any cache.

Private: Indicates that all or part of the response message for a single user cannot be processed by the shared cache. This allows the server to only describe a partial response from a user that is not valid for other users' requests.

no-cache: Indicates that the request or response message cannot be cached

no-store: Used to prevent important information from being released unintentionally. Sending it in the request message will cause both the request and response messages to use caching.

max-age: Indicates that the client can receive responses with a lifetime no greater than the specified time in seconds.

min-fresh: Indicates that the client can receive responses with a response time less than the current time plus the specified time.

max-stale: Indicates that the client can receive response messages beyond the timeout period. If you specify a value for max-stale messages, the client can receive response messages that exceed the specified value of the timeout period.

After reading this article, if you encounter similar problems, you will be able to completely solve them. Please remember that this solution is only for PHP websites.

Original address: http://www.manongjc.com/article/600.html

Related reading:

php implements receiving multiple form data instances with the same name but different values

php obtain form data example sharing

php A complete form validation example

Two ways to submit form in php

jQuery formValidator form validation

A simple form validation example with jquery

Several ways to prevent repeated submission of forms in php

Detailed explanation of usage of js form onsubmit event

jquery A complete non-refresh ajax submission form example

jquery uses ajax to submit the form

php uses curl to simulate post submission

php simulates form post submission through fsockopen

php form $_POST[] example application

Share a common JavaScript method to verify whether the form is empty

php form submitted to this page

Several ways to get form elements in javascript

javascript A complete form validation example

Use js to submit form

Example application of form form in php

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/1115253.htmlTechArticleSolution to the problem of returned data disappearing after php form submission error, php form This article introduces php form to coders The solution to the problem of returning data disappearing after submitting an error. If you are interested...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn