PHP is bad but more bad and not corrected is a bad Header. Here to Remove Expires: Thu, 19 Nov 1981 PHP Header in Ubuntu Server running Apache or Nginx. Why Apache2 or Nginx, practically it will work for any web server software that can run PHP. This is not a problem of WP Super Cache or any PHP software developer. Credit (pun intended) is of PHP. It is tad hard to know what actually add this stuff. PHP is bad, if you want to read more.
Why Remove Expires: Thu, 19 Nov 1981 PHP Header in Ubuntu Server
To encourage caching, in short. This is 2015, may be you will read this in 3015, PHP will continue this thing. If Expire Header is in minus years, it simply means Caching is discouraged. It is birthday of the developer and responsible who compiled the PHP.ini. How much it deliver pain on Shared Hosting, it is very difficult to say. On our Setup, we need to Edit all the nodes manually. His father and mother had successful sexual reproduction and gave him birth on that day, thats why he added. He could add an X-Header : Parents-Sexually-Active.
That is his birthday. He has a worst PHP.net looking website and claims as Magento Expert. Very small person, telling the name has big problem – he has 2 followers on GitHub, 281 Known on LinkedIn. He will become popular. From WordPress Cache Plugin to a simple script, human get confused what to do. We are giving two options to remove Expires Thu, 19 Nov 1981 PHP Header in Ubuntu Server. Other Linux distro will have kind of same method. The moron’s work add more problem with HSTS and plain HTTPS and SSL.
Adding Internationally notable, honored person like Linus Trovalis or Richard M. Stallman was practical, if he had a moral. None in this World would complain if the date was 25th December, all zero. Any religion will honor Jesus Christ’s sayings, way of life. You will not find anything on his website – it says in excerpt, he is a big moron and you should hire him.
It has hundreds of variants as output depending on MIME type. Suppose, if ob_start('ob_gzhandler') is called after the line session_cache_limiter() it can overwrite cache control headers in any combination. This is reference of the function :
1 | http://php.net/manual/en/function.session-cache-limiter.php |
Head will get more hot, if you see the table’s header – “Possible values”. Possible values? Possible values because changing the setting might not work as defined.
Remove Expires: Thu, 19 Nov 1981 PHP Header in Apache2 Server (Shared Environment)
You have no control of PHP.ini in shared hosting. Now, how’ll change? This is a problem which can not explained unless you are a Linux Admin running 700 accounts on one IP. Do not blame the Linux Admin or Hosting. Change in PHP.ini can open up security issues. On dedicated instances, we can control many things. Thankfully you have .htaccess file. This is the actual place :
1 | http://httpd.apache.org/docs/2.2/mod/mod_expires.html |
---
It will go away if you add :
1 | ExpiresActive Off |
then force MIME type expires.
Very difficult problem, custom solution is needed for your problem.
Remove Expires: Thu, 19 Nov 1981 PHP Header Nginx, Apache, Whatever with root Access
Do not try to fix the library. Right method which we are describing – to edit PHP.ini file. SSH as root. To find the right PHP.ini, run this command :
1 | php -i | grep 'Configuration File' |
You will get output like :
1 2 | Configuration File (php.ini) Path => /etc/php5/cli Loaded Configuration File => /etc/php5/cli/php.ini |
Editing the first will work fine, but Edit the CLI one too, depending on Need. If you want to list all the PHP related INI (if you running PHP-FPM fallback with HHVM, for example), run this :
1 | locate php.ini |
You will get output like this :
1 2 3 4 | /etc/hhvm/php.ini /etc/php5/cgi/php.ini /etc/php5/cli/php.ini /etc/php5/fpm/php.ini |
Open the file with nano, we do not need vi for this small work, we are imbecile, our death of birth is not important, hence nano.
Hit ^ and W if it is a Mac and type this ==> cache_limiter and hit the Enter / Return key and you’ll find these :
1 year = 31536000 seconds
1 year = 525600 minutes
You will edit :
1 2 3 4 5 | session.cache_limiter = public, max-age= ; Document expires after n minutes. ; http://php.net/session.cache-expire session.cache_expire = 180 |
Make it to :
1 2 | session.cache_limiter = public, max-age = 525600 session.cache_expire = 525600 |
Restart the PHP services (PHP5-FPM or whatever) and Nginx or Apache2 or may be, you can reboot. HHVM is no good, they copy-pasted from PHP.net’s website :
1 | http://docs.hhvm.com/manual/en/function.session-cache-limiter.php |
But, you can override with value in /etc/hhvm/config.hdf. Do not try to edit any session.c like settings file. when a production server will die, you’ll understand why PHP is bad.
