| Re: HTTP_REFERER Error |
| by allnewtome on 2006/1/21 3:30:05 I've had the same problem and have typed up a (potential) solution here: https://xoops.org/modules/newbb/viewtopic.php?topic_id=45943&start=0#forumpost202503 Hope it helps. P.S. This might sound a bit rude (sorry), but there are loads of threads about this subject so perhaps we could all reply to the one linked to above? |
| Re: HTTP_REFERER Error |
| by Khepri on 2005/12/30 0:00:05 Did you try adding the www. to this?; define('XOOPS_ROOT_PATH', '/public_html/domain.com/site2'); Seem like it is passing that to the browser and you get that weird redirect. I don't seem to have that problem as my wehost uses a user name there instead of a domain name.... |
| Re: HTTP_REFERER Error |
| by JamesSAEP on 2005/12/29 19:25:56 Ok, after further investigation, the redirect to the "http://domain.com/site2" only happens on the initial page load. If you click any of the Main Menu links (Home, Newbb, News, etc) the browser address has the "http://www." added. So, this seems to be only a problem on the initial site load. Any thoughts? |
| Re: HTTP_REFERER Error |
| by JamesSAEP on 2005/12/29 17:15:36 I'm still having this problem with one of my sites. I have my primary site: http://www.domain.com/site1 which works fine when I type the url into a browser. My second site is installed in a second folder at: http://www.domain.com/site2 and this is the one that has a problem. When I type in the full ulr http://www.domain.com/site2 the browser is redirected to http://domain.com/site2. As soon as I login, the browser is then redirected to the url with "http://www.domain.com/site2" and gives the HTTP_REFER error. The mainfile.php does have the correct settings: define('XOOPS_ROOT_PATH', '/public_html/domain.com/site2'); define('XOOPS_URL', 'http://www.domain.com/site2'); 1. Why would this misdirection happen? 2. Is there a way to put in a htaccess that will direct it to the url with the "http://www." ? Thanks. |
| Re: HTTP_REFERER Error |
| by Khepri on 2005/12/29 0:40:28 I'm getting this after running the update script (to 2.2.3a) on a 2.0.13.1 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 http://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 http://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 UPDATE2: 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 http://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 http://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 2.0.13.2..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 http://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. http://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. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|