Hi,

I think this issue was related to this module; however, I was also creating Deltas and Contexts via the Omega theme. Reading the below, do you think this module was the culprit?

I filled out the "IP address to use for testing" field with "127.0.0.1" - this is probably totally the wrong thing to do - I'm kinda flailing in the dark with this!

Afterwards, I checked my site, and it had lost it's images, and the Omega theme stopped working, as well as the administration menu module. I ended up checking the Apache error log. It was showing a multitude of errors of the type: "[error] [client 127.0.0.1] client denied by server configuration: /path/to/a/variety/of/web/site/files/on/server".

FYI, I fixed it by adding "Allow from 12.0.0.1" to the sites' .htaccess file (per http://blog.f12.no/wp/2005/06/01/apache-client-denied-by-server-configur...). Would this be ok on a live site, or is there a security issue involved?

Thanks. Again, not sure it was Smart IP and my flailing-type configuration; it just seems to be the most likely.

Comments

arpeggio’s picture

arpeggio commented
Status: Active » Postponed (maintainer needs more info)

Hi malcolm, sorry for the late reply. The IP spoofing at Smart IP admin page will just populate the $_SESSION['smart_ip']['location'] and $user->data['geoip_location'] variables, and I don't think these variables will have impact on the Omega theme.

FYI, I fixed it by adding "Allow from 12.0.0.1" to the sites' .htaccess file (per http://blog.f12.no/wp/2005/06/01/apache-client-denied-by-server-configur...). Would this be ok on a live site, or is there a security issue involved?

What exactly did you put in your .htaccess?

malcolm’s picture

malcolm commented

Currently, the .htaccess file in my sites folder contains exactly:

SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Deny from all
Allow from all
Options None
Options +FollowSymLinks
heddn’s picture

heddn
Primary language English
Location Illinois
commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Drupal 7 is no longer supported in a month. Closing old issues. If this is still an issue in the current 5.x version of the module, please re-open and provide some next steps.