Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #43308, comment 6


Ignore:
Timestamp:
02/14/2018 02:48:51 PM (7 years ago)
Author:
youngcp
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #43308, comment 6

    initial v1  
    1818It's already "hold my beer," but let's see what we can do about controlling non-authenticated access and allowing the result to be cached. Nonces prevent caching, so any variation of is straight out. Anything that generates a lot of potential URL patterns for the same request is out.
    1919
    20 So there needs to be a no-cache interstitial that can't be hammered at load-scripts and load-styles with a cache-friendly redirect that takes a generated key (maybe a hash) that combines the unique load request and some validation salt to prevent guessing (easy enough). I think I can do that.
     20So there needs to be a no-cache interstitial that can't be hammered at load-scripts and load-styles with a cache-friendly redirect (a 301 with long expiry) that takes a generated key (maybe a hash) that combines the unique load request and some validation salt to prevent guessing (easy enough). I think I can do that.
    2121
    2222Replying to [comment:5 azaozz]: