Php – How to create a url in a wordpress that will return code 200

google-cloud-platformPHPWordpress

This is needed because I need to implement a load balancer in GCP for a word press instance.

GCP will only forward a request to the wordpress instance if it passes the health test.

Here is a typical of definition of a health check screen

It expects the 'request path' to return 200. Otherwise the target system is considered down.

However if I create a page in wordpress e.g. /index.php/newpage, it will always return 301.

While the wordpress site is up and running, it fails the health check.

Is there any way I can define a page in wordpress that will return 200? Hopefully it will not require additional plugin because I would like avoid maintaining extra plugin.

The last resort to me is to add a url to the php server that will return 200. However the status of this url may not 100% reflect the health of the wordpress site (which may go down due to mysql issue for example). If it is indeed the last resort, what is the best way to implement it? I am not proficient with php developement.

The version of wordpress is 4.6.2

Best Answer

You can use your WordPress installation front page for the health check. This is the most reliable indicator that the WordPress site is available.

Related Solutions

Optimize High Traffic WordPress Website – Best Practices

I think your biggest downfall will be doing this on a virtualised system. I wouldn't put a high traffic site on a shared host, of any kind.

I'd want a dedicated server, because that way, I could guarantee that I could prioritise the system processes to handle the IO for the website, not having to worry about whatever the server was doing for other users.

MT's dedicated-virtual server sounds like an oxymoron.. Which is it? Dedicated, or Virtual? You can't have both, unless you're the only VM on a host server, in which case, what's the point?

I'd probably want to scale out, too.. get a pair of servers, do mysql circular replication between them, loadbalance and cache with Varnish. Back these applications onto a server with fast disks(600GB SAS), and Lots of RAM (16GB+).

RAM is cheap now, and Varnish will use lots of it to speed up delivery of your assets. You'll notice a massive increase in speed. DB writes will also be faster because of the faster disks.

Try to keep logging and database partitions on separate disks, so the logging (sequential, mostly) access isn't interrupted by database access (random reads and writes)

Nginx rewrite rules, fastcgi and WordPress – 404 pages due to REQUEST_URI

Try this

server {
  error_page   405   = @handler;
  error_page   404   = @handler;

  location / {
    if (-f $request_filename) {
      break;
    }

    if (!-e $request_filename) {
      rewrite . /index.php last;
    }
  }

  location @handler { 
    rewrite / /index.php;
  }

  location ~ \.php/ {
    rewrite ^(.*.php)/ $1 last;
  }

  location ~ \.php$ {
    if (!-e $request_filename) { rewrite / /index.php last; }

    fastcgi_pass   127.0.0.1:9000;
    fastcgi_index  index.php;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    include        fastcgi_params;
  }

}

And in your fastcgi_params

fastcgi_param  QUERY_STRING       $query_string;
fastcgi_param  REQUEST_METHOD     $request_method;
fastcgi_param  CONTENT_TYPE       $content_type;
fastcgi_param  CONTENT_LENGTH     $content_length;

fastcgi_param  SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param  REQUEST_URI        $request_uri;
fastcgi_param  DOCUMENT_URI       $document_uri;
fastcgi_param  DOCUMENT_ROOT      $document_root;
fastcgi_param  SERVER_PROTOCOL    $server_protocol;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param  REMOTE_ADDR        $remote_addr;
fastcgi_param  REMOTE_PORT        $remote_port;
fastcgi_param  SERVER_ADDR        $server_addr;
fastcgi_param  SERVER_PORT        $server_port;
fastcgi_param  SERVER_NAME        $server_name;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param  REDIRECT_STATUS    200;

Related Topic