I have been searching for some configurations of .htaccess, filters and hooks to make able to manage the inner site uri’s. The goal was force login, register and admin pages through SSL, and all the other pages through HTTP.

Although it can be easy when you have the same domain for both, http and https, it could be quite difficult when the domain is different, and even the PATH different (for example: HTTP on mydomain.com/blog, and HTTPS on mydomain.sslserver.com).

Neither this question (Use a different domain for SSL) nor the HTTPS PlugIn, helped to reach this goal with success.
For this reason I began making my own customization taking advantage of some other information.

The problem is I am very new with WordPress code, and trying to find out how the redirection works, I am stuck without understanding the inner WordPress redirection.

Then, my question:
If the RewriteRule does not pass the PATH of the permalink (for example, a path to a post or a category), and only is rewriting to /index.php, how can this file ‘knows’ which is the queried post or category?

I supposed that in some part of the code it would need use the $_SERVER[“REQUEST_URI”] or the $_SERVER[‘REQUEST_URI’] or the $_SERVER[‘ORIG_PATH_INFO’] somewhere, since it works without converting the permalink’s PATH to a QueryString, and without sending any POST or GET data.

Please, I have been seeking for some tutorial telling what is going on and did not find any thing with a clear and plane explanation. Maybe there are too many pages of close information related and the Searcher do not show me the correct page, maybe I am not searching correctly, but I really need to know how it works.

Thanks!

Read more here: Once redirected by Rewrite rules, how can WordPress know the page?


Solution:

If you know the solution of this issue, please leave us a reply in Comment section, to update the question.

Related Wordpress search:

, , , ,

Wordpress related questions and answers: