Ticket #579 (closed defect: worksforme)

Opened 4 months ago

Last modified 7 weeks ago

400 Bad Request Cross Site Action detected

Reported by: BradChesney79 Owned by: padams
Priority: trivial Milestone:
Component: base module Version: 1.4
Keywords: cross site action Cc:

Description

I have analytics downloaded to the outward facing server connected to the innerwebs using NAT via a dd-wrt flashed netgear wnr-3500l router. I thought this was the problem, not so.

The files are located in the /var/www/ssl/owa directory. ssl is the webroot and is only accessible via the https protocol. i386/Debian 6.0/apache2/php5

The database is on a separate machine, it seems to be fine when things don't crash hardcore. It is accessed via a non-routable IP 192.x.x.x on the same subnet.

I have tried permissions up to 777.
I have used various owners and groups consisting of ([root]|[user]|[www-data]):([root]|[user]) combinations.

The things I thought I needed to do to correct this broke the script hardcore and now I am getting nowhere with ferocious velocity. Reinstalling did not help. I will try again later.

Change History

Changed 4 months ago by admin

Sounds like a routing error to me. There is no bug related to running the DB on a separate host.

Changed 4 months ago by BradChesney79

Maybe it is a routing error? But there should be no routing during installation short of the DB entries-- which are created in between monkeying with settings most of the time.

I will probably use the most basic features of OWA. I don't know that I have need for the cross site metrics-- for now can I just turn them off in a config file or a parameter sent to the install script?

If cross site features can be turned off, maybe it can be off by default for installation and then turned on much later in the installation.

Changed 7 weeks ago by admin

  • status changed from new to closed
  • resolution set to worksforme
Note: See TracTickets for help on using tickets.