Is setting Expires Header in .htacess a terrible idea for a Woocommerce site?











up vote
0
down vote

favorite












I have added the following to my .htacces file in order to set the expiry time for the various files types. The speed impact on my woocommerce site has been huge - it's flying now. And everything seems to work.



But surely this is a bad idea as if all the script files, thumbnails etc are cached then things shouldn't work properly one editing the cart / returning customers etc?



It just seems too easy??



# Optimize cache-control

<IfModule mod_expires.c>

    ExpiresActive on

    ExpiresDefault "access plus 1 month"

    ExpiresByType image/gif "access plus 1 month"

    ExpiresByType image/png "access plus 1 month"

    ExpiresByType image/jpg "access plus 1 month"

    ExpiresByType image/jpeg "access plus 1 month"

    ExpiresByType text/html "access plus 3 days"

    ExpiresByType text/xml "access plus 1 seconds"

    ExpiresByType text/plain "access plus 1 seconds"

    ExpiresByType application/xml "access plus 1 seconds"

    ExpiresByType application/rss+xml "access plus 1 seconds"

    ExpiresByType application/json "access plus 1 seconds"

    ExpiresByType text/css "access plus 1 week"

    ExpiresByType text/javascript "access plus 1 week"

    ExpiresByType application/javascript "access plus 1 week"

    ExpiresByType application/x-javascript "access plus 1 week"

    ExpiresByType image/x-ico "access plus 1 year"

    ExpiresByType image/x-icon "access plus 1 year"

    ExpiresByType application/pdf "access plus 1 month"

  <IfModule mod_headers.c>

       Header unset ETag

       Header unset Pragma

       Header unset Last-Modified

       Header append Cache-Control "public, no-transform, must-revalidate"

       Header set Last-modified "Tue, 1 Nov 2018 10:10:10 GMT"

  </IfModule>

</IfModule>





.htaccess woocommerce expires-header







share|improve this question


























    up vote
    0
    down vote

    favorite












    I have added the following to my .htacces file in order to set the expiry time for the various files types. The speed impact on my woocommerce site has been huge - it's flying now. And everything seems to work.



    But surely this is a bad idea as if all the script files, thumbnails etc are cached then things shouldn't work properly one editing the cart / returning customers etc?



    It just seems too easy??



    # Optimize cache-control
    
<IfModule mod_expires.c>
    
    ExpiresActive on
    
    ExpiresDefault "access plus 1 month"
    
    ExpiresByType image/gif "access plus 1 month"
    
    ExpiresByType image/png "access plus 1 month"
    
    ExpiresByType image/jpg "access plus 1 month"
    
    ExpiresByType image/jpeg "access plus 1 month"
    
    ExpiresByType text/html "access plus 3 days"
    
    ExpiresByType text/xml "access plus 1 seconds"
    
    ExpiresByType text/plain "access plus 1 seconds"
    
    ExpiresByType application/xml "access plus 1 seconds"
    
    ExpiresByType application/rss+xml "access plus 1 seconds"
    
    ExpiresByType application/json "access plus 1 seconds"
    
    ExpiresByType text/css "access plus 1 week"
    
    ExpiresByType text/javascript "access plus 1 week"
    
    ExpiresByType application/javascript "access plus 1 week"
    
    ExpiresByType application/x-javascript "access plus 1 week"
    
    ExpiresByType image/x-ico "access plus 1 year"
    
    ExpiresByType image/x-icon "access plus 1 year"
    
    ExpiresByType application/pdf "access plus 1 month"
    
  <IfModule mod_headers.c>
    
       Header unset ETag
    
       Header unset Pragma
    
       Header unset Last-Modified
    
       Header append Cache-Control "public, no-transform, must-revalidate"
    
       Header set Last-modified "Tue, 1 Nov 2018 10:10:10 GMT"
    
  </IfModule>
    
</IfModule>





    .htaccess woocommerce expires-header







    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have added the following to my .htacces file in order to set the expiry time for the various files types. The speed impact on my woocommerce site has been huge - it's flying now. And everything seems to work.



      But surely this is a bad idea as if all the script files, thumbnails etc are cached then things shouldn't work properly one editing the cart / returning customers etc?



      It just seems too easy??



      # Optimize cache-control
      
<IfModule mod_expires.c>
      
    ExpiresActive on
      
    ExpiresDefault "access plus 1 month"
      
    ExpiresByType image/gif "access plus 1 month"
      
    ExpiresByType image/png "access plus 1 month"
      
    ExpiresByType image/jpg "access plus 1 month"
      
    ExpiresByType image/jpeg "access plus 1 month"
      
    ExpiresByType text/html "access plus 3 days"
      
    ExpiresByType text/xml "access plus 1 seconds"
      
    ExpiresByType text/plain "access plus 1 seconds"
      
    ExpiresByType application/xml "access plus 1 seconds"
      
    ExpiresByType application/rss+xml "access plus 1 seconds"
      
    ExpiresByType application/json "access plus 1 seconds"
      
    ExpiresByType text/css "access plus 1 week"
      
    ExpiresByType text/javascript "access plus 1 week"
      
    ExpiresByType application/javascript "access plus 1 week"
      
    ExpiresByType application/x-javascript "access plus 1 week"
      
    ExpiresByType image/x-ico "access plus 1 year"
      
    ExpiresByType image/x-icon "access plus 1 year"
      
    ExpiresByType application/pdf "access plus 1 month"
      
  <IfModule mod_headers.c>
      
       Header unset ETag
      
       Header unset Pragma
      
       Header unset Last-Modified
      
       Header append Cache-Control "public, no-transform, must-revalidate"
      
       Header set Last-modified "Tue, 1 Nov 2018 10:10:10 GMT"
      
  </IfModule>
      
</IfModule>





      .htaccess woocommerce expires-header







      share|improve this question













      I have added the following to my .htacces file in order to set the expiry time for the various files types. The speed impact on my woocommerce site has been huge - it's flying now. And everything seems to work.



      But surely this is a bad idea as if all the script files, thumbnails etc are cached then things shouldn't work properly one editing the cart / returning customers etc?



      It just seems too easy??



      # Optimize cache-control
      
<IfModule mod_expires.c>
      
    ExpiresActive on
      
    ExpiresDefault "access plus 1 month"
      
    ExpiresByType image/gif "access plus 1 month"
      
    ExpiresByType image/png "access plus 1 month"
      
    ExpiresByType image/jpg "access plus 1 month"
      
    ExpiresByType image/jpeg "access plus 1 month"
      
    ExpiresByType text/html "access plus 3 days"
      
    ExpiresByType text/xml "access plus 1 seconds"
      
    ExpiresByType text/plain "access plus 1 seconds"
      
    ExpiresByType application/xml "access plus 1 seconds"
      
    ExpiresByType application/rss+xml "access plus 1 seconds"
      
    ExpiresByType application/json "access plus 1 seconds"
      
    ExpiresByType text/css "access plus 1 week"
      
    ExpiresByType text/javascript "access plus 1 week"
      
    ExpiresByType application/javascript "access plus 1 week"
      
    ExpiresByType application/x-javascript "access plus 1 week"
      
    ExpiresByType image/x-ico "access plus 1 year"
      
    ExpiresByType image/x-icon "access plus 1 year"
      
    ExpiresByType application/pdf "access plus 1 month"
      
  <IfModule mod_headers.c>
      
       Header unset ETag
      
       Header unset Pragma
      
       Header unset Last-Modified
      
       Header append Cache-Control "public, no-transform, must-revalidate"
      
       Header set Last-modified "Tue, 1 Nov 2018 10:10:10 GMT"
      
  </IfModule>
      
</IfModule>





      .htaccess woocommerce expires-header




      .htaccess woocommerce expires-header






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 6 hours ago









      user2894986

      4019




      4019





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371318%2fis-setting-expires-header-in-htacess-a-terrible-idea-for-a-woocommerce-site%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371318%2fis-setting-expires-header-in-htacess-a-terrible-idea-for-a-woocommerce-site%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Can a sorcerer learn a 5th-level spell early by creating spell slots using the Font of Magic feature?

          Image
          28 6 $begingroup$ Per the Font of Magic feature, sorcerer can use Flexible Casting to create 5th-level spell slots at level 7, even though they are not typically available until level 9. You can transform unexpended sorcery points into one spell slot as a bonus action on your turn. The Creating Spell Slots table shows the cost of creating a spell slot of [5th level is 7] If such a sorcerer levels up while still having this 5th-level spell slot, can they choose a 5th-level spell as the spell they gain upon levelling up? The Spellcasting feature states: Additionally, when you gain a level in this class, you can choose one of the sorcerer spells you know and replace it with another spell from the sorcerer spell list, which also must be of a level for which you have spell slots.
          Read more

          ts Property 'filter' does not exist on type '{}'

          Image
          1 I'm trying to follow Angular Material guide to create a custom filter for autocomplete input text https://material.angular.io/components/autocomplete/overview This is what I have TS import { Component, OnInit } from '@angular/core'; import { TemplateRef } from '@angular/core'; import { FormControl } from "@angular/forms"; import { Observable } from "rxjs"; import { map, startWith, filter } from 'rxjs/operators'; (...) export class AppComponent implements OnInit { title = 'Your Profile'; displayedColumns: string = ['selected', 'name', 'description', 'pnr']; dataSource = ELEMENT_DATA; myControl = new FormControl(); options: any = ['One', 'Two', 'Three']; filteredOptions:
          Read more

          mat-slide-toggle shouldn't change it's state when I click cancel in confirmation window

          Image
          1 When I checked the slide toggle it should work as expected. But when I try to uncheck it there is a confirmation window asking if you are sure. When I click cancel in that confirmation window, still the toggle changes to unchecked, which shouldn't happen. It should stay in the same state. Here is my Html and TS Code // html <mat-slide-toggle (change)="change($event)" [checked]="isChecked()" > To-pay </mat-slide-toggle> TS code: // ts change(e) { if(this.checked) { if(confirm("Are you sure")) { console.log("toggle") } else { e.stopPropagation(); console.log("toggle should not change if I click the cancel button") }
          Read more