Cookie cookies are a great invention that allows web developers to keep their users ' login status. However, when your site or network
There is a problem when you have more than one domain name.
In the cookie specification, a cookie can be used only for one domain name and not for other domain names. Therefore, if you are in the browser
A domain name is set up with a cookie that is not valid for other domain names. If you want to get your users from one of your sites
One to log in, but also to log on to other domains, which is really a big problem.
My solution will use the following general framework:
A preset script is used to accept SessionID numbers passed through a GET or cookie. It will take precedence over cookies to select get
Variable. So whenever we need to refer to the cross domain name, we send SessionID as a URL parameter.
Modifies the Apache configuration to implement a cookie that overrides all cross domain names. The reason for this will be clear in a moment.
Use variables at any time when a cross domain reference is present.
First step: Create a preset script
Add the following code to the Out-of-the-box script (or to a function that appears before all the scripts).
<?php
/* Support cross Domain cookie ... * *
If the get variable is already set, and it is different from the cookie variable
You use a Get variable (update cookie)
Global $http_cookie_vars, $http_get_vars;
if (Isset ($sessionid) && isset ($http_get_vars[\ ' sessionid\ ']) && ($http_cookie_vars[\ ' sessionid\ ']! = $http_get_vars[\ ' sessionid\ ']) {
Setcookie (\ ' sessionid\ ', $http_get_vars[\ ' sessionid\ '), 0, \ '/\ ', \ ' \ ');
$http_cookie_vars[\ ' sessionid\ '] = $http_get_vars[\ ' sessionid\ '];
$sessionid = $http_get_vars[\ ' sessionid\ '];
}
?>
Once this code is run, a global \ ' sessionid\ ' variable will be available for scripting. It will be saved in the user's cookie
SessionID value, or a SessionID value that is sent through a GET request.
Step two: Use variables for all cross domain references
Create a global configuration file that holds the basic reference form for domain names that can be toggled. For example, if we have
Domain1.com and Domain2.com, the following settings are:
<?php
$domains[\ ' domain1\ ' = "http://www.domain1.com/-$sessionid-";
$domains[\ ' domain2\ ' = "http://www.domain2.com/-$sessionid-";
?>
Now, if you do the following in your code:
<?php
echo "Click <a href=\" ", $domains[\ ' domain2\ '", "/contact/?email=yes\" >here</a> to contact us. "
?>
You will produce the following output:
Click <a href= "Http://www.domain2.com/-66543afe6543asdf6asd-/contact/?email=yes\" >here</a>
To contact us.
Here SessionID has been inserted into the URL.
In this place, you might think, "this might open a subdirectory on the Web server named horizontal, SessionID, horizontal?!?!?."
However, the steps below will provide a necessary trick to make it work!
Step Three: Configure Apache
Now, the next step is to configure Apache to rewrite the URL:
http://www.domain2.com/-66543afe6543asdf6asd-/contact/
Become this:
Http://www.domain2.com/contact/?sessionid=66543afe6543asdf6asd
And this URL:
Http://www.domain2.com/-66543afe6543asdf6asd-/contact/?email=yes
Become this:
Http://www.domain2.com/contact/?email=yes&sessionid=66543afe6543asdf6asd
To implement it, simply configure two virtual servers as domain1 and Domain2, as follows:
<virtualhost ipaddress>
Documentroot/usr/local/www/domain1
ServerName www.domain1.com
Rewriteengine on
Rewriterule ^/-(. *)-(. *\?). *) $ $2&sessionid=$1 [L,R,QSA]
Rewriterule ^/-(. *)-(. *) $ $2?sessionid=$1 [L,R,QSA]
</VirtualHost>
<virtualhost ipaddress>
Documentroot/usr/local/www/domain2
ServerName www.domain2.com
Rewriteengine on
Rewriterule ^/-(. *)-(. *\?). *) $ $2&sessionid=$1 [L,R,QSA]
Rewriterule ^/-(. *)-(. *) $ $2?sessionid=$1 [L,R,QSA]
</VirtualHost>
These overridden rules implement the requirements of the above two URL overrides.
Conclusion
Cross-domain cookies can be implemented in a simple way by using variable binding with Apache rewrite capabilities. Want to maintain such a
System, no matter when the link cross domain name, in the use of domain name variables, nothing to do! Links within the domain name are not required
Modified, because cookies will work properly.
If you are interested in looking at the actual operating system in the production network, please visit http://www.familyhealth.com.au/. In
Move your mouse over some cross domain links and see how they are rewritten when you click.
Perhaps the only problem with this technique is that you cannot delete cookies under all the domain names in the user's browser.
