Fixed WordPress connection under IIS6-php Tutorial

Wordpress fixed connection under IIS6 makes me step on a day's pitfall. after fixed connection, use {code ...} you can access the category, but after I write it to RewriteRule, it will always report 404 {code ...} because I used the global URLRewrite configuration, I found that I had to write RewriteRule {generation... wordpress fixed connections under IIS6 let me step on a day's pitfall. after Fixed Connections, use

/index.php?category_name=php

Can access the category, but after I write it to RewriteRule, the old report is 404.

RewriteRule ^/program/(.*) /index.php\?category_name=$1 [L]

Because I used the global URLRewrite configuration, I found that the RewriteRule should be written like this one day later.

RewriteRule ^/program/(.*) /index.php/program\?category_name=$1 [L]

However, it is hard to figure out how this 404 code came from. even if WP jumped to 404 in that line of code, it could not be found. the execution process of WP made me crazy.

Reply content:

Wordpress fixed connections under IIS6 let me step on a day's pitfall. after Fixed Connections, use

/index.php?category_name=php

Can access the category, but after I write it to RewriteRule, the old report is 404.

RewriteRule ^/program/(.*) /index.php\?category_name=$1 [L]

Because I used the global URLRewrite configuration, I found that the RewriteRule should be written like this one day later.

RewriteRule ^/program/(.*) /index.php/program\?category_name=$1 [L]

However, it is hard to figure out how this 404 code came from. even if WP jumped to 404 in that line of code, it could not be found. the execution process of WP made me crazy.

You still use the outdated IIS6. it's strange that you don't step on it.
Cannot I use Apache or Nginx?

I really don't understand what the reason for using the win host is