1. 08 May, 2017 1 commit
  2. 13 Apr, 2017 1 commit
  3. 12 Apr, 2017 1 commit
  4. 05 Apr, 2017 1 commit
  5. 20 Mar, 2017 1 commit
  6. 16 Mar, 2017 1 commit
  7. 09 Mar, 2017 1 commit
  8. 22 Feb, 2017 1 commit
  9. 26 Jan, 2017 1 commit
  10. 23 Jan, 2017 2 commits
  11. 22 Jan, 2017 3 commits
  12. 19 Jan, 2017 1 commit
  13. 18 Jan, 2017 2 commits
  14. 14 Jan, 2017 3 commits
  15. 05 Jan, 2017 1 commit
  16. 14 Dec, 2016 1 commit
  17. 28 Nov, 2016 2 commits
  18. 22 Nov, 2016 1 commit
  19. 18 Nov, 2016 1 commit
  20. 01 Nov, 2016 1 commit
  21. 31 Oct, 2016 1 commit
  22. 27 Oct, 2016 1 commit
  23. 26 Oct, 2016 1 commit
    • Michael Olbrich's avatar
      souphttpsrc: reset read_position when reading fails · 8666b7d8
      Michael Olbrich authored
      souphttpsrc maintains two variables for the position:
       * 'request_position' is where we want to be
       * 'read_position' is where we are
      During Normal operations both are updated in sync when data arrives. A seek
      changes 'request_position' but not 'read_position'.
      When the two positions get out of sync, then a new request is send and the
      'Range' header is adjusted to the current 'request_position'.
      
      Without this patch, if reading fails, then the source is destroyed. This
      triggers a new request, but the range remains unchanged. As a result, the
      old range is used and old data will be read.
      
      Changing the 'read_position' to -1 makes it explicitly different from
      'request_position' and as a result the 'Range' header is updated correctly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=773509
      8666b7d8
  24. 26 Sep, 2016 1 commit
  25. 24 Sep, 2016 1 commit
  26. 18 Sep, 2016 1 commit
  27. 15 Sep, 2016 1 commit
  28. 13 Sep, 2016 1 commit
  29. 06 Sep, 2016 1 commit
  30. 26 Aug, 2016 2 commits
  31. 20 Aug, 2016 1 commit
  32. 25 Jul, 2016 1 commit