1. 19 Jan, 2017 1 commit
  2. 18 Jan, 2017 2 commits
  3. 14 Jan, 2017 3 commits
  4. 05 Jan, 2017 1 commit
  5. 14 Dec, 2016 1 commit
  6. 28 Nov, 2016 2 commits
  7. 22 Nov, 2016 1 commit
  8. 18 Nov, 2016 1 commit
  9. 01 Nov, 2016 1 commit
  10. 31 Oct, 2016 1 commit
  11. 27 Oct, 2016 1 commit
  12. 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
  13. 26 Sep, 2016 1 commit
  14. 24 Sep, 2016 1 commit
  15. 18 Sep, 2016 1 commit
  16. 15 Sep, 2016 1 commit
  17. 13 Sep, 2016 1 commit
  18. 06 Sep, 2016 1 commit
  19. 26 Aug, 2016 2 commits
  20. 20 Aug, 2016 1 commit
  21. 25 Jul, 2016 1 commit
  22. 12 Jul, 2016 1 commit
    • Edward Hervey's avatar
      souphttpsrc: Don't drop final bytes of a range request · 1d55fbce
      Edward Hervey authored
      At the end of a range request, we don't want to return GST_FLOW_EOS otherwise
      the last bytes we just read will be dropped by basesrc.
      
      Instead just return GST_FLOW_OK (which was set just before) and let basesrc
      handle the fact we are at the end of the segment.
      1d55fbce
  23. 11 Jul, 2016 2 commits
    • Sebastian Dröge's avatar
      souphttpsrc: At the end of a range request, read another time to finalize the request · e6823e4d
      Sebastian Dröge authored
      If we're at the end of a range request, read again to let libsoup
      finalize the request. This allows to reuse the connection again later,
      otherwise we would have to cancel the message and close the connection.
      e6823e4d
    • Sebastian Dröge's avatar
      souphttpsrc: Fix keep-alive handling · b1edc286
      Sebastian Dröge authored
      We have to get rid of the message on EOS when the complete stream is read to
      remember that we successfully finished handling this specific message.
      Otherwise we will cancel it later and close the connection instead of reusing
      it at a later time.
      
      It might also make sense to reuse connections if a non-200 response is
      received. As long as there was no connection error, the HTTP connection should
      be re-usable.
      b1edc286
  24. 08 Jul, 2016 2 commits
  25. 29 Jun, 2016 2 commits
  26. 17 Jun, 2016 1 commit
  27. 08 Jun, 2016 2 commits
  28. 06 Jun, 2016 1 commit
  29. 03 Jun, 2016 3 commits