By mitylite on

I've taken a look at my database logs and its absolutely filled with endless 404 page not found warnings for crossdomain.xml and I have no idea why. As far as I know, no modules im using require this. I searched drupal.org and all the related posts seem to be with various flash based media modules but I am not using these, and never have. Infact the only flash content I have is facebook videos that are embedded in body fields using facebook embed code.

What's with all the requests for this mysterious page?

Thanks for reading.

The warning itself:

"page not found 01/10/2011 - 19:19 crossdomain.xml Anonymous"

There's no more information than that given about it.

⋅ Categories: Drupal 6.x

Comments

mcfilms’s picture

mcfilms commented

It's pretty standard to have a request for a cross-domain policy inside a Flash file. So these files are what are causing it. You might be able to get away with just putting an empty document in your root and naming crossdomain.xml. Otherwise you'll need to actually create an xml document and specify facebook.com (and any other sites) are allowed to access your site.

A list of some of the Drupal sites I have designed and/or developed can be viewed at motioncity.com

mitylite’s picture

mitylite commented

hmmm, and what kind of problems could a blank file cause do you think?

mcfilms’s picture

mcfilms commented

None that I can think of. Just not sure if it will prevent the errors. One way to find out...

A list of some of the Drupal sites I have designed and/or developed can be viewed at motioncity.com

mitylite’s picture

mitylite commented

Yeah it seems to have put an end to them, thanks mcfilms.

AimAdvantage’s picture

AimAdvantage commented

I also think this may be a root domain issue-

In other words- I am working on a site in maintenance mode and if you enter with the www. prefix - no problems-

If you login without the www.prefix - I believe it is trying to access the crossdomain.xml file to treat the site links the same with or without the www. prefix.

Anyone else experience this in maintenance mode?

Not sure if I stated this exactly correct - but one admin user is experiencing this and I think it has to do with the www. prefix settings for the root domain.

Thanks
Aaron