1
As with Markus, I'm running XOOPS 2.2 English on my notebook through localhost, so there shouldn't be a firewall issue. I didn't get this error when I ran XOOPS 2.0.9. I'm running MAMP, on which Apache is running on port 8888, not port 80. If the REFERER_BLOCKED message stems from a port issue, can XOOPS be adjusted to ignore the port if the webserver is a localhost? I'd rather not change my Apache and MySQL port settings on my development notebook.
Quote:
Quote:
organix wrote:
Quote:
Herko Coomans wrote:
you're not doing anything wrong, that's the first thing to say. However, it should work, so we have to look at the cause of this.
First of all, you are using 2.0.13 non-english, and are upgrading to 2.2. The HTTP_REFERRER_BLOCKED error is triggered when a database query fails and the HTTP REFERER check also fails. So make sure that your localhost is added to the 'trusted sites' list of your software firewall (this being the most common cause for the HTTP REFERRER info being blocked).
With that fixed, we can proceed to what is causing the query to fail.
Herko
I have no firewall (XP firewall is deactivated) and my 2.0.13 was english as the 2.2 too. Remember, my testsite is on localhost (127.0.0.1) and most firewalls don't block anything on this adapter.
But, I think I've found the reason for the problem and it seems to me a bug or a bad feature in the XOOPS update procedure. My webservers on both computers weren't running on port 80, that was the problem and looks to me like a bug.
Now I've changed my webserver to port 80 and the update script works.
But more. After the update I changed my webserver back to port 85 and on every login the referer block error message with hints on firewalls etc. do occur. It's not a big problem, but it shows that the referer checking in xoops-2.2 have problems with webservers not running on port 80.
I never had such problems with 2.0.x versions of XOOPS and I'm not sure if this referer block checking in 2.2 was a good idea.
regards
Markus
