| Commit message (Expand) | Author | Age | Files | Lines |
* | Http cache: Avoid resuming (and keeping) truncated entries | rvargas@google.com | 2010-01-08 | 1 | -4/+15 |
* | Http cache: Add code to restart a network request when the | rvargas@google.com | 2009-12-01 | 1 | -1/+3 |
* | Revert 33133 - Http cache: Add code to restart a network request when the | rvargas@google.com | 2009-11-30 | 1 | -3/+1 |
* | Http cache: Add code to restart a network request when the | rvargas@google.com | 2009-11-25 | 1 | -1/+3 |
* | Add compiler-specific "examine printf format" attributes to printfs. | evan@chromium.org | 2009-11-20 | 1 | -6/+10 |
* | Http cache: Always preserve extra headers when dealing with | rvargas@google.com | 2009-11-03 | 1 | -4/+6 |
* | Minor defense-in-depth tweak. end - start + 1 can actually go negative if | cevans@chromium.org | 2009-10-28 | 1 | -1/+1 |
* | Http Cache: More unit tests for byte range support. | rvargas@google.com | 2009-10-14 | 1 | -0/+4 |
* | Handle range request on a truncated entry | hclam@chromium.org | 2009-10-02 | 1 | -3/+2 |
* | Handle reading to the end of a sparse entry | hclam@chromium.org | 2009-10-01 | 1 | -0/+3 |
* | Bug fixing for range request support in HttpCache | hclam@chromium.org | 2009-09-05 | 1 | -1/+1 |
* | Http Cache: Add support for resuming downloading a | rvargas@google.com | 2009-09-04 | 1 | -4/+35 |
* | Http cache: Fix the code that handles 206s when revalidating | rvargas@google.com | 2009-08-20 | 1 | -3/+0 |
* | Http Cache: Additional byte-range support. | rvargas@google.com | 2009-08-18 | 1 | -11/+59 |
* | Http cache: Extend support for byte range requests. | rvargas@google.com | 2009-08-12 | 1 | -17/+36 |
* | Http cache: Add support for ranges with an unknown start or end. | rvargas@google.com | 2009-06-24 | 1 | -19/+31 |
* | Http cache: Return valid Content-Range headers for a byte range request. | rvargas@google.com | 2009-06-22 | 1 | -0/+75 |
* | Http Cache: First pass of byte-range requests support. | rvargas@google.com | 2009-06-12 | 1 | -0/+131 |