 
      
    | You are here | blog.octo.com | ||
| | | | | zhero-web-sec.github.io | |
| | | | | CVE-2024-46982 | |
| | | | | www.speakeasy.com | |
| | | | | Designing an API with cacheability in mind produces a more sensible and better separated set of resources, and it just so happens to be more performant, cheaper, and better for the environment. | |
| | | | | www.mnot.net | |
| | | | | A long, long time ago, I wrote some tests using XmlHttpRequest to figure out how well browser caches behaved, and wrote up the results. | |
| | | | | robertnyman.com | |
| | | Updated April 20th I'm so used to having a $ method for accessing elements. Nevertheless, the idea is of course that FlashReplace should be stand-alone, so I replaced it with the standard document.getElementById. Updated April 20th Although I didn't encounter any problems with not using an embed element (to have valid HTML code output), it | ||