Posted on: 2005/12/29 0:40
Re: HTTP_REFERER Error
I'm getting this after running the update script (to 2.2.3a) on a 22.214.171.124 install....
Here's the difference...I've run the update on three installs with no trouble (in the end..LOL)...
But the fourth install, doing the exact same thing yeild the http_referrer error....
The difference? The fourth install is on a server that has a private SSL cert installed on it. It was installed on www.site.com
, but I notice that XOOPS keeps stripping the www out and redirecting to site.com...and I get the error...
The tech that installed the cert suggested to put it under www.site.com
...I email the servers support but I'm thinking their going to say it's a XOOPS problem...which judging by this thread I'm inclined to believe...:)
Is this a DNS issue? Or is it something in XOOPS?
UPDATE: Upon further investigation I find that XOOPS "works" as long as I stick with the site.com format URI...the second www is prepended the warnings start....on 2.2.3a
I tried switching authentication method to LDAP...now I'm locked out of the site because the LDAP module won't load...
I also installed to subdomain.site.com...works great!
The issue seem to be XOOPS NOT treating www.site.com
and site.com as one in the same...
If I log into site.com...all is okay...while logged in if I migrate via the address bar in the FF browser to www.site.com...it
wants me to login again. Which of course, it won't let me, because upon submitting the login I get redirected to site.com with a error message that it's the wrong password....
I think I'm just going to go baCK TO 126.96.36.199..disappointed.
UPDATE3: NAH, SCREW THAT! I'm going to make this work...it works on another domain install to webroot!
Any suggestions are appreciated...
UPDATE4: This appears to have corrected the situation somewhat...I'm not getting the http_referrer warning anymore....however if I attempt to login at site.com instead of www.site.com
it doesn't know who I am...
This is from the FAQ;
"This could be caused by not having the XOOPS_URL and/or PHYSICAL_PATH in mainfile.php set to exactly where the website is located. This means that redirects do not work, as XOOPS checks the URL you logged into to the URL you are at, and if the base URL doesn't match (ie. www.xoops.org
vs. xoops.org without www), you're not recognised as logged in."
Mine said "site.com"...it gave me http_referrer warning...I changed it to "www.site.com
" (which matches a CNAME in my DNS) I no longer get the warning and redirect does indeed work now...that'll work for now...but there should be a way to handle that discrepency...imo.