Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The only modules you need loaded by apache for wordpress are the following... this excludes your php module and I'll explain that a bit more after:</p> <pre><code>LoadModule authz_host_module modules/mod_authz_host.so LoadModule log_config_module modules/mod_log_config.so LoadModule expires_module modules/mod_expires.so LoadModule deflate_module modules/mod_deflate.so LoadModule env_module modules/mod_env.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule mime_module modules/mod_mime.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule dir_module modules/mod_dir.so LoadModule alias_module modules/mod_alias.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule headers_module modules/mod_headers.so </code></pre> <p>Depending on whether you are running php fcgi or php mod_php (prefork) then you would include one of the following:</p> <pre><code>#---- For FPM of PHP Enable both below and disable php5_module LoadModule fastcgi_module modules/mod_fastcgi.so LoadModule actions_module modules/mod_actions.so #---- For standard php5 module enable below and disable 2 above #LoadModule php5_module modules/libphp5.so </code></pre> <p>The redirects that I'm seeing based on your log output looks more like a badly configured mod_rewrite rule, or a 301 redirect plugin in wordpress that is conflicting with rules on apache.</p> <p>Now as a general rule of thumb, when we host namevirtualhost based vhosts, we create a <em>default</em> vhost with Servername default</p> <p>And set it's doc root to a directory that includes 1 html file and rewrite rule to transfer all traffic to the index.html (The html file just outputs <em>hosted by</em>) That way you filter out all of the garbage traffic that isn't based on your domain itself, and since it's only running html it doesn't require any iops based on php as it's static html only.</p> <p>That way your vhost will only handle requests for the domain that it hosts. Now that doesn't fix the issue with 301's that are happening. If you can share your mod_rewrite configuration then perhaps there is something in there that we can help with.</p> <p>The biggest problem I've seen in the community with SSL based traffic is when the developers have to integrate with load balancers where the SSL certificate is truncated on the load balancer instead of apache. With that said you can no longer do a rewrite condition / rule to check if https != on, redirect 301 to a new location as the load balancer terminates the cert and sends http (port 80) traffic to your webhost so apache will always think it's unencrypted even though it hits a <em>secured</em> vhost</p> <p>One additional note on your vhost. It's better to not use .htaccess files unless you <em>ABSOLUTELY</em> have to. For wordpress a vhost directory element should look something like this for optimal performance.</p> <pre><code>&lt;VirtualHost *:80&gt; ServerName www.example.com DocumentRoot /path/to/doc_root &lt;Directory /path/to/doc_root/&gt; AllowOverride None Options SymLinksIfOwnerMatch MultiViews -Indexes Order allow,deny Allow from all RewriteEngine On RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^.*$ index.php [L] &lt;/Directory&gt; &lt;/VirtualHost&gt; </code></pre> <p>The reason why I say optimal performance is that the .htaccess file does not get read by apache on every single request that comes to it. It instead reads it as part as vhost config and saves the configuration in memory so essentially you save a huge amount on iops by not having it use a .htaccess in addition to additional security of not having to rely on .htaccess files and overrides.</p> <p>And finally using RewriteBase is irrelevant and sometimes just causes prolems unless you host wordpress under a specific alias like /blog/ In your case based on your .htaccess file it appears to be on the base domain so there is no need to have that directive in there. For reference see the rewrite rules i have in the vhost config above.</p>
    singulars
    1. This table or related slice is empty.
    1. PORedirect loop on attempted web proxy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWill H
    1. USWill H
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORedirect loop on attempted web proxy
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COnice answer. Maybe you should add some emphasis on the default vhost part.
      singulars
      1. PO
      1. USregilero
    2. COThanks for your reply. This was pretty insightful. I think I'll setup a default host and see if that helps. As far as not using `.htaccess`, I'm pretty sure WordPress requires the setup to be as such. The `.htaccess` file is automatically generated by WordPress when you configure it through the web interface.
      singulars
      1. PO
      1. USDane Hillard
    3. COYes it's generated automatically but you do not need it. You can add the same rules directly in the vhost. Thats how we run all our wordpress instances :P Glad it helped you out.
      singulars
      1. PO
      1. USWill H
 

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