• lorty@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    15 days ago

    I can’t be the only one who has wasted half an hour wondering why something wasn’t working before realising the response was cached.

  • unalivejoy@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    I checked the headers. This answer is cached.

    age: 72
    cache-control: max-age=600
    x-cache: HIT
    x-cache-hits: 2
    
    • thejml@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 days ago

      There are two hard problems in computing, naming things, cache invalidation, and off by one errors.

    • PM_Your_Nudes_Please@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      15 days ago

      I once had a problem that wasn’t caused by caching. It was caused by Accounts Payable forgetting to pay the internet bill, and the ISP cutting our service halfway through a network test. So the beginning of the test cached that the network had internet access, but then the end of the- wait fuck it was caused by caching