1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Moving Apache to Nginx not affect Wordpress core/system files?

Discussion in 'BlackHat Lounge' started by PCTag, May 28, 2013.

  1. PCTag

    PCTag Junior Member

    Joined:
    Jun 25, 2011
    Messages:
    124
    Likes Received:
    8
    Home Page:
    I'm considering to move from Apache to Nginx to improve performances. I read few how to tutorials, but they are not mentioned anything about WordPress file system. All of them mentioned server side steps.

    Once I installed Nignix on my VPS should I modify or change my WordPress core files (wp-config.php. etc and database? Or is it just server installation?

    Thanks.
     
    Last edited: May 28, 2013
  2. henriduf

    henriduf Registered Member

    Joined:
    Mar 18, 2012
    Messages:
    58
    Likes Received:
    11
    Home Page:
    It is a major mistake to move nginx. Apache has been proven to be stable and it is the most important.

    I am suspicious about all this things around nginx. I have extensively tried to compare Apache vs Nginx performance but i have never been successful in finding that nginx was faster. Nginx used only less memory but i don't want to sacrifice stabilty over memory.

    On top of that, and it is an information i only share with blahatworlders. The 301 redirect pages of the nginx servers are not in compliance with RF2616. There is no link inside the redirect page. They only use location in http headers. So, if you get a drop of traffic after moving to nginx it can be due to standard pages from Nginx.

    Here is the 301 redirect page of nginx:
    Code:
    <html>
    
    <head><title>301 Moved Permanently</title></head>
    
    
    <body bgcolor="white">
    
    
    <center><h1>301 Moved Permanently</h1></center>
    
    
    <hr><center>nginx/1.7.7</center>
    
    
    </body>
    
    
    </html>
    Here is the 301 redirect of Apache:
    Code:
    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head>
    <title>301 Moved Permanently</title>
    </head><body>
    <h1>Moved Permanently</h1>
    <p>The document has moved <a href="http://www.infoworld.com/article/2612082/open-source-software/has-apache-lost-its-way-.html">here</a>.</p>
    </body></html>

    Also, the configuration files of nginx are a mess. it is much more complicated than Apache and when it does not work you get 502 errors all the time.

    Stick to Apache & learn to optimize your apache web server by unloading modules if you really have a specific use of Apache.

    If you look into the biggest websites on the internet, NONE of them switched to nginx. (Amazon, Ebay, facebook, twitter, tumblr.....)


    About the propaganda:
    When there is a website that BS on Apache and encourage you to move to nginx, look at their headers, look at the html of their 404 to know their web server. You will discover the vast majority of them use Apache, IIs but never nginx.
     
    Last edited: Dec 12, 2014
  3. emild331

    emild331 Registered Member

    Joined:
    Dec 12, 2014
    Messages:
    60
    Likes Received:
    4
    hedriduf, are you serious? Apache isn't built for high traffic. Switch to nginx, or apache+nginx works aswell. You'll notice the speed immidentily.
     
  4. blackice6666

    blackice6666 Regular Member

    Joined:
    Nov 20, 2014
    Messages:
    233
    Likes Received:
    92
    I would suggest moving to Nginx only if you have a lot of traffic and you dont have the resources (Memory) to handle that traffic. Otherwise Apache is really stable and has a lot of modules which can come in handy in the future.

    However, you might still give an other chance to apache by fine-tuning its configuration in order to get better performance. You can also use "Google Page Speed" Apache module which will dramatically increase the overall performance.

    Regarding your question about WP configuration you just have to make sure that the memory limit in wordpress is smaller than the memory limit in php.ini

    If you dont have a memory limit set on your wordpress config than you can just ignore the recommendation above.