1. 07 Aug, 2011 1 commit
  2. 06 Aug, 2011 9 commits
  3. 02 Aug, 2011 2 commits
  4. 21 Jul, 2011 1 commit
  5. 19 Jul, 2011 1 commit
  6. 05 Jul, 2011 2 commits
  7. 03 Jul, 2011 1 commit
  8. 27 Jun, 2011 1 commit
  9. 17 Jun, 2011 1 commit
  10. 05 Jun, 2011 3 commits
  11. 04 Jun, 2011 4 commits
  12. 02 Jun, 2011 1 commit
    • If you start multiple ASIHTTPRequests from different threads at the same time, you could encounter a condiition where networkThread is being multiply initialized
      Florent Pillet authored
  13. 28 May, 2011 8 commits
  14. 19 May, 2011 1 commit
  15. 16 May, 2011 1 commit
  16. 15 May, 2011 3 commits
    • ASIDownloadCache will now store 301, 302, 303 and 307 redirect responses in the cache. Requests pulling from the cache will automatically redirect (assuming shouldRedirect is true) as if they'd received a Location header from the server.
      This change should allow the download cache to operate more effectively as an offline fallback when no internet connection is available.
      Additionally, requests encountering a 304 will no longer read from the cache and then write back to it. Instead, they merely update the expiry date (if an updated date was supplied).
      As part of this work, two new required methods were added to the ASICacheDelegate protocol, see ASICacheDelegate.h for more info
      Finally, ASIDownloadCache now stores the response status code in a custom header in the cached headers dictionary, and requests will have their response status code set to this when they are pulled from the cache.
      Ben Copsey authored
    • …celLoad if the whole download is complete
      * Also, don't clear responseHeaders in cancelLoad
      
      closes gh-182
      Ben Copsey authored
    • Ben Copsey authored