Home  >  Article  >  Backend Development  >  Summary of access mode, path access mode and URL rewriting of pathinfo in ThinkPHP, thinkphppathinfo_PHP tutorial

Summary of access mode, path access mode and URL rewriting of pathinfo in ThinkPHP, thinkphppathinfo_PHP tutorial

WBOY
WBOYOriginal
2016-07-13 10:20:15962browse

Summary of access mode, path access mode and URL rewriting of pathinfo in ThinkPHP, thinkphppathinfo

This article summarizes the two modes of pathinfo, the four path access modes and URL rewriting related knowledge in ThinkPHP, and shares it with everyone for easy inquiry and reference. The specific summary is as follows:

1. pathinfo

Access the test method under the module IndexAction.class.php

http://localhost/index.php?m=Index&a=test is equivalent to http://localhost/index.php/Index/test

2. Four path access modes

Modify the URL_MODEL value under the config directory, as follows:

A value of 0 is called normal mode. For example: http://localhost/index.php?m=module&a=method
A value of 1 is called pathinfo mode. Such as: http://localhost/index.php/module/method
A value of 2 is called rewrite (pseudo-static). You can write the relevant rewrite rules yourself, or you can use the rewrite rules provided by the system to hide index.php and generate: http://localhost/module/method
A value of 3 is called compatibility mode. When the server does not support the pathinfo mode, but you use the previous path access format, all use the pathinfo format. Then it will prompt you that the path format is incorrect. Then, you can use the compatibility mode numbered 3 to deal with it. His path access is similar to http://localhost/index.php?s=module/method

3. URL rewriting steps:

(1), D:wampwampApache2confhttpd.conf turns on the URL_REWRITE module in the apache server

(2), AllowOverride None Change None to All

(3). Ensure that URL_MODEL in the config.php configuration file is set to 2

(4). Place the .htaccess file in the same directory as the entry file
 
Using URL rewriting is beneficial to SEO, but it will increase the performance consumption of the server.

I hope this article will be helpful to everyone in ThinkPHP programming.

Issues related to ThinkPHP’s url path access mode

can be obtained using $_GET
For example,
index.php/action/function/id/2

$_GET[cation] is function

$ _GET[id] is 2

Understand? It’s just that the form has been changed, but the value is the same

What are the differences between thinkphp’s four URL modes in url access, not to mention those functions such as URL rewriting?

localhost/think/index.php/Index/index is a pseudo-static URL address, in order to make the page better crawled by search engines. Search engines prefer static pages. Another feature of dynamic pages is that they have a ? number, so they are removed when written like this.

localhost/...=index This one is the most original access method. Typical dynamic web page URL address. Not search engine friendly.

localhost/think/index.php/Index/index?id=1 This is a pseudo-static compatibility writing method. Some servers do not support pseudo-static, so they are written like this.

There is another way you didn’t mention: localhost/think/index/Index/index. It is the rewrite function of apache and needs to enable the rewrite module. However, some servers are not turned on, and turning it on will increase the server's resource consumption.

Summary: You can add the extension of static pages such as .html or .htm after the pseudo-static to make the pseudo-static more perfect. The TP framework has such a function, please study it.

Note: rewrite is actually a type of pseudo-static.

www.bkjia.comtruehttp: //www.bkjia.com/PHPjc/868228.htmlTechArticleA summary of the access mode, path access mode and URL rewriting of pathinfo in ThinkPHP, thinkphppathinfo This article focuses on the two aspects of pathinfo in ThinkPHP Three modes, four path access modes and URL rewriting are related...
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