5 ms·

The commit ID seems to be part of the URL you can use https://raw.githubusercontent.com/burekasKodi/repository.burekasKodi/0440dafb4450b235bc3ea25767804d237288

• Aeolun 4y ago
  I’m not fine with latest not actually being latest. That defeats the point of the URL.
  • IanCal 4y ago
    I get the issue but I do strongly feel that you should expect http resources to be cached. It's so common of a thing expecting it to never be cached is unreasonable as a design. I would expect the headers to make this clear, however.
    • Aeolun 4y ago
      I actually don’t. Git already has a file on the filesystem. Serving a plain file is as close to caching as you are going to get.
  • 8note 4y ago
    There's a hard limit on that - the speed of light. You can't know what the actual latest is, only some cached value. The actual value may have changed while the message is in flight
    • xboxnolifes 4y ago
      Guess we may as well throw our handa up in the air then and set a 14 year cache ttl.