Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Magento uses .htaccess files in various directories to deny access to the directory trees. You will find them in app, media, var, and wherever else Magento sees fit to stick them. They do various things like deny viewing (app, var), executing (media .htaccess). For these .htaccess files to work, it is really important that the following be set in either the doc root .htaccess or in the virtual server configuration.</p> <pre><code>Options FollowSymLinks AllowOverride All </code></pre> <p>More than likely, Magento detects that the app directory .htaccess file isn't being allowed to deny network access to your app/etc/local.xml file, so all your database credentials and encryption key are visible to anyone with a web browser.</p> <p>Another issue might be that your file/directory permissions are too lax.</p> <p>For Magento running under FastCGI, SuPHP or LSAPI</p> <pre><code>find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; chmod 550 pear #for Magento pre 1.5 chmod 550 mage #for Magento 1.5 and up chmod 550 cron.sh </code></pre> <p>For Magento running under DSO (mod_php)</p> <pre><code>find . -type f -exec chmod 644 {} \; find . -type d -exec chmod 755 {} \; chmod o+w var var/.htaccess app/etc chmod 550 pear #for Magento pre 1.5 chmod 550 mage #for Magento 1.5 and up chmod 550 cron.sh chmod -R o+w media </code></pre> <p><strong>For the question below,</strong> the app/etc folder is supposed to have the following .htaccess file in place. Trying to read anything through the server should throw a 403 error. Your next step is to get in touch with your web hoster to find out why that file is not being honored.</p> <pre><code>Order deny,allow Deny from all </code></pre> <p><strong>Note:</strong> If you are using alternative http servers like nginx, you must search down all of the .htaccess files created in Magento's directory tree and recreate all the .htaccess functions used by Magento in your nginx setups so you have the same file/directory protections as a standard Apache DSO install. Same goes for Windows installations on IIS.</p>
    singulars
    1. This table or related slice is empty.
    1. POMagento Apache configuration (app/etc/local.xml accessible warning)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFiasco Labs
    1. USFiasco Labs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMagento Apache configuration (app/etc/local.xml accessible warning)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have any idea what might resolve the issue if I've taken both these steps and the file is still publicly accessible? I've verified that apache rewrite is enabled as well.
      singulars
      1. PO
      1. USDarth Egregious
    2. COSee above final paragraph. Check to see if that .htaccess file is in place and then find out why your web server isn't obeying directives for very basic security.
      singulars
      1. PO
      1. USFiasco Labs
    3. COThanks. For anyone who is having trouble beyond the answer above, I found it helpful to check my apache error log. It pointed out that I had a problem in my .htaccess file in /var/www. I didn't really need this file, so removing it resolved the issue.
      singulars
      1. PO
      1. USDarth Egregious
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload