Hello....
I´ve seen various threads about this problem... I tried to answer in them, but for my surprise, next day my post was deleted... Don´t know what happened or if I did something wrong, so I´ll start a new thread...
In the post "Addon Domains URL Bar problem" Link, it´s possible to fix just editing the httpd.conf, because the problem has it´s origin at Cpanel configuring only a "servername" for the subdomain, not for the addon domain... when Apache searchs for the document or folder, it turns the URL into "servername" + "/" + folder + "/"....
I already know it was the problem since I´ve done my own tests just having a look at what Cpanel do....
There´s also a thread, with the magical sollution... just telling clients to add an .htaccess with mod_rewrite sentences, just to translate subdomains into domains... well, it doesn´t function... already tested into subdomain folder and public_html folder.. both of us can override at all with .htaccess files... apache translation still works...
So, finally the sollution is just editing httpd.conf adding the "servername" correctly.... well....
Now imagine I´m a hoster, with almost 60 hosts, and maybe 5000 addon domains, in the 60 httpd.confssss..... well, the problem is maybe bigger than at the beginning.
I´m I supposed to write an script in perl to search for addon domains and replace servernames in the httpd.conf?? a bit difficult..... I guess... and the problem will be still, since new addon domains will appear... mmm... a cron job? pfff....
Well, Cpanel developers already know about this problem, or the might know I guess since it´s fully reported...
Ok... it´s not a problem of Apache, it´s a problem the way Cpanel modify httpd.conf, in other words, maybe the Cpanel developers can modify a few scripts just to do it right?? maybe one update will solve this problems??? An addon domain is independent from the account one, so many clients are being affected since clients of the clients would see a wrong URL in their navigators... IT´S NOT QUITE IMPORTANT?
I hope developers take this into priority task, because maybe it´s fully and easily fix-able....
So I say, please, fix it...
I´ve seen various threads about this problem... I tried to answer in them, but for my surprise, next day my post was deleted... Don´t know what happened or if I did something wrong, so I´ll start a new thread...
In the post "Addon Domains URL Bar problem" Link, it´s possible to fix just editing the httpd.conf, because the problem has it´s origin at Cpanel configuring only a "servername" for the subdomain, not for the addon domain... when Apache searchs for the document or folder, it turns the URL into "servername" + "/" + folder + "/"....
I already know it was the problem since I´ve done my own tests just having a look at what Cpanel do....
There´s also a thread, with the magical sollution... just telling clients to add an .htaccess with mod_rewrite sentences, just to translate subdomains into domains... well, it doesn´t function... already tested into subdomain folder and public_html folder.. both of us can override at all with .htaccess files... apache translation still works...
So, finally the sollution is just editing httpd.conf adding the "servername" correctly.... well....
Now imagine I´m a hoster, with almost 60 hosts, and maybe 5000 addon domains, in the 60 httpd.confssss..... well, the problem is maybe bigger than at the beginning.
I´m I supposed to write an script in perl to search for addon domains and replace servernames in the httpd.conf?? a bit difficult..... I guess... and the problem will be still, since new addon domains will appear... mmm... a cron job? pfff....
Well, Cpanel developers already know about this problem, or the might know I guess since it´s fully reported...
Ok... it´s not a problem of Apache, it´s a problem the way Cpanel modify httpd.conf, in other words, maybe the Cpanel developers can modify a few scripts just to do it right?? maybe one update will solve this problems??? An addon domain is independent from the account one, so many clients are being affected since clients of the clients would see a wrong URL in their navigators... IT´S NOT QUITE IMPORTANT?
I hope developers take this into priority task, because maybe it´s fully and easily fix-able....
So I say, please, fix it...