Heim  >  Artikel  >  Backend-Entwicklung  >  Nach der Bereitstellung des Typecho-Frameworks tritt beim Zugriff auf interne Seiten ein 404-Fehler auf.

Nach der Bereitstellung des Typecho-Frameworks tritt beim Zugriff auf interne Seiten ein 404-Fehler auf.

WBOY
WBOYOriginal
2016-12-01 00:25:432978Durchsuche

Nachdem das Typecho-Framework bereitgestellt wurde, tritt beim Zugriff auf interne Seiten ein 404-Fehler auf

Webserver Nginx

Nginx-Konfiguration

<code># You may add here your
# server {
#    ...
# }
# statements for each of your virtual hosts to this file

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    #root /usr/share/nginx/html;
    root /home/pog/www;
    index index.php index.html index.htm;

    # Make site accessible from http://localhost/
    #server_name localhost;
    server_name www.517557.com;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ =404;
        # Uncomment to enable naxsi on this location
        # include /etc/nginx/naxsi.rules
    }

    # Only for nginx-naxsi used with nginx-naxsi-ui : process denied requests
    #location /RequestDenied {
    #    proxy_pass http://127.0.0.1:8080;    
    #}

    #error_page 404 /404.html;

    # redirect server error pages to the static page /50x.html
    #
    #error_page 500 502 503 504 /50x.html;
    #location = /50x.html {
    #    root /usr/share/nginx/html;
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        try_files $uri = 404;
    #    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    #    # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
    #
    #    # With php5-cgi alone:
    #    fastcgi_pass 127.0.0.1:9000;
    #    # With php5-fpm:
        fastcgi_pass unix:/var/run/php5-fpm.sock;
        fastcgi_index index.php;
        fastcgi_split_path_info ^(.+\.php)(.*)$;
        fastcgi_param PATH_INFO $fastcgi_path_info;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny all;
    #}
}


# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
#    listen 8000;
#    listen somename:8080;
#    server_name somename alias another.alias;
#    root html;
#    index index.html index.htm;
#
#    location / {
#        try_files $uri $uri/ =404;
#    }
#}


# HTTPS server
#
#server {
#    listen 443;
#    server_name localhost;
#
#    root html;
#    index index.html index.htm;
#
#    ssl on;
#    ssl_certificate cert.pem;
#    ssl_certificate_key cert.key;
#
#    ssl_session_timeout 5m;
#
#    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
#    ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES";
#    ssl_prefer_server_ciphers on;
#
#    location / {
#        try_files $uri $uri/ =404;
#    }
#}
</code>
Fehlerphänomen

Nach der Bereitstellung des Typecho-Frameworks tritt beim Zugriff auf interne Seiten ein 404-Fehler auf.

Nginx-Protokoll

<code>121.22.72.122 - - [26/Nov/2016:20:38:14 +0800] "GET /favicon.ico HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) C
735 121.22.72.122 - - [26/Nov/2016:20:38:17 +0800] "GET /index.php/archives/1/ HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, lik
736 121.22.72.122 - - [26/Nov/2016:20:38:21 +0800] "GET /index.php/archives/1/ HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, lik
737 111.251.93.1 - - [26/Nov/2016:20:39:45 +0800] "CONNECT mx-tw.mail.gm0.yahoodns.net:25 HTTP/1.0" 400 181 "-" "-"
738 121.22.72.122 - - [26/Nov/2016:20:44:34 +0800] "GET / HTTP/1.1" 200 2279 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0
739 121.22.72.122 - - [26/Nov/2016:20:50:11 +0800] "GET /index.php/start-page.html HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTM</code>
Antwortinhalt:

Nachdem das Typecho-Framework bereitgestellt wurde, tritt beim Zugriff auf interne Seiten ein 404-Fehler auf

Webserver Nginx

Nginx-Konfiguration

Fehlerphänomen
<code># You may add here your
# server {
#    ...
# }
# statements for each of your virtual hosts to this file

##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# http://wiki.nginx.org/Pitfalls
# http://wiki.nginx.org/QuickStart
# http://wiki.nginx.org/Configuration
#
# Generally, you will want to move this file somewhere, and start with a clean
# file but keep this around for reference. Or just disable in sites-enabled.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    #root /usr/share/nginx/html;
    root /home/pog/www;
    index index.php index.html index.htm;

    # Make site accessible from http://localhost/
    #server_name localhost;
    server_name www.517557.com;

    location / {
        # First attempt to serve request as file, then
        # as directory, then fall back to displaying a 404.
        try_files $uri $uri/ =404;
        # Uncomment to enable naxsi on this location
        # include /etc/nginx/naxsi.rules
    }

    # Only for nginx-naxsi used with nginx-naxsi-ui : process denied requests
    #location /RequestDenied {
    #    proxy_pass http://127.0.0.1:8080;    
    #}

    #error_page 404 /404.html;

    # redirect server error pages to the static page /50x.html
    #
    #error_page 500 502 503 504 /50x.html;
    #location = /50x.html {
    #    root /usr/share/nginx/html;
    #}

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #
    location ~ \.php$ {
        try_files $uri = 404;
    #    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    #    # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
    #
    #    # With php5-cgi alone:
    #    fastcgi_pass 127.0.0.1:9000;
    #    # With php5-fpm:
        fastcgi_pass unix:/var/run/php5-fpm.sock;
        fastcgi_index index.php;
        fastcgi_split_path_info ^(.+\.php)(.*)$;
        fastcgi_param PATH_INFO $fastcgi_path_info;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }

    # deny access to .htaccess files, if Apache's document root
    # concurs with nginx's one
    #
    #location ~ /\.ht {
    #    deny all;
    #}
}


# another virtual host using mix of IP-, name-, and port-based configuration
#
#server {
#    listen 8000;
#    listen somename:8080;
#    server_name somename alias another.alias;
#    root html;
#    index index.html index.htm;
#
#    location / {
#        try_files $uri $uri/ =404;
#    }
#}


# HTTPS server
#
#server {
#    listen 443;
#    server_name localhost;
#
#    root html;
#    index index.html index.htm;
#
#    ssl on;
#    ssl_certificate cert.pem;
#    ssl_certificate_key cert.key;
#
#    ssl_session_timeout 5m;
#
#    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
#    ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES";
#    ssl_prefer_server_ciphers on;
#
#    location / {
#        try_files $uri $uri/ =404;
#    }
#}
</code>

Nach der Bereitstellung des Typecho-Frameworks tritt beim Zugriff auf interne Seiten ein 404-Fehler auf.Nginx-Protokoll

<code>121.22.72.122 - - [26/Nov/2016:20:38:14 +0800] "GET /favicon.ico HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) C
735 121.22.72.122 - - [26/Nov/2016:20:38:17 +0800] "GET /index.php/archives/1/ HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, lik
736 121.22.72.122 - - [26/Nov/2016:20:38:21 +0800] "GET /index.php/archives/1/ HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, lik
737 111.251.93.1 - - [26/Nov/2016:20:39:45 +0800] "CONNECT mx-tw.mail.gm0.yahoodns.net:25 HTTP/1.0" 400 181 "-" "-"
738 121.22.72.122 - - [26/Nov/2016:20:44:34 +0800] "GET / HTTP/1.1" 200 2279 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0
739 121.22.72.122 - - [26/Nov/2016:20:50:11 +0800] "GET /index.php/start-page.html HTTP/1.1" 404 208 "http://www.517557.com/" "Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTM</code>
Wo ist das Fehlerprotokoll?

Um Pseudostatik zu aktivieren

Wenn es sich um lnmpa handelt, können Sie die .htaccess-Umleitung direkt festlegen. Wenn es sich um Lnmp handelt, können Sie versuchen, typecho.conf einzuschließen

Stellungnahme:
Der Inhalt dieses Artikels wird freiwillig von Internetnutzern beigesteuert und das Urheberrecht liegt beim ursprünglichen Autor. Diese Website übernimmt keine entsprechende rechtliche Verantwortung. Wenn Sie Inhalte finden, bei denen der Verdacht eines Plagiats oder einer Rechtsverletzung besteht, wenden Sie sich bitte an admin@php.cn