1. 28 May, 2018 1 commit
  2. 20 May, 2018 1 commit
  3. 07 May, 2018 1 commit
    • Philipp Schafft's avatar
      Feature: Generate errors based on IDs. · b42378ab
      Philipp Schafft authored
      This generates error pages based on IDs. This allows to reuse errors
      and add more advanced information to them.
      This patch also makes Icecast send in plain text OR HTML based
      on the clients Accept:-string.
  4. 06 May, 2018 1 commit
  5. 05 May, 2018 1 commit
    • Philipp Schafft's avatar
      Fix: Fixed regression for ICY source client's auth · bcc0e86c
      Philipp Schafft authored
      This allows ICY source clients to log in again with 2.4.x-style config.
      ICY does not provide a username. Therefore the username was unset.
      This patch sets the username for ICY source connections and allow them
      to be handled as if a username was provided.
      Configuration tag <shoutcast-user> was added to select the username to set
      to. This defaults to "source".
  6. 21 Apr, 2018 1 commit
  7. 13 Apr, 2018 1 commit
  8. 23 Jul, 2017 9 commits
  9. 23 Nov, 2015 1 commit
  10. 22 Nov, 2015 2 commits
  11. 01 Mar, 2015 2 commits
  12. 10 Feb, 2015 4 commits
    • Philipp Schafft's avatar
    • Philipp Schafft's avatar
      Feature: Support PUT with chunked transfer encoding. · 36d10121
      Philipp Schafft authored
      This adds the Transfer-Encoding chunked to PUT support.
      Please test carefully. Will add PUT to Allow: header after testing.
      Have fun.
      Closes: #2088
    • Philipp Schafft's avatar
      Cleanup: unbreak 100-continue a bit. · 79cb147c
      Philipp Schafft authored
      This tries to unbreak the 100-continue thing a bit.
      Proper headers are send in case of 100-continue. Also the 200 OK
      was moved to the end of the stream.
      The client may even be reused. But I'm not sure we only do
      'End of stream' in cases we are not on an undefined state of the
      client. Do we as of now support anything that give us EOS without
      a fatal socket state (error or shutdown)?
      At least this unbreaks 100-continue with active TLS that was broken
      as hell as we sent the header in clear over the socket. Not checking
      if it was transmitted completly or something. Using lowlevel socket
      calls (in contrast to the connection level calls that would have
      handled the TLS just fine).
      While this seem sto be a huge improvement to the situation I kindly
      ask you to do a lot testing on this. Both with SOURCE as well as
      PUT clients.
    • Philipp Schafft's avatar
      Fix/Cleanup: Answer SOURCE/PUT requests with a real 200-OK. · d6908eb0
      Philipp Schafft authored
      We have answered SOURCE/PUT requests with a simple
      "HTTP/1.0 200 OK\r\n\r\n" while we should answer with complet
      headers. This commit corrects this.
      This will work for two classes of clients:
       * Super dumb ones not checking the response and will just send
         data and hope the socket is still open.
       * Those with a real parser.
       * Shoutcast clients (indepnded code path).
       * All libshout, curl, wget, ... based clients.
      This *could* break:
       * Clients that check for the exact returned message. However
         as we start with the same string this should work.
         Only client that check for the string including the End-of-header
         CRLF sequense may break.
      Please test careful before release.
  13. 06 Feb, 2015 1 commit
  14. 02 Feb, 2015 3 commits
  15. 01 Feb, 2015 2 commits
  16. 25 Jan, 2015 1 commit
    • Marvin Scholz's avatar
      Cleanup codestyle · 0dfc7c5b
      Marvin Scholz authored
      This commit cleanups codestyle a bit, yet there is still some work to be done
  17. 10 Jan, 2015 2 commits
  18. 05 Jan, 2015 1 commit
  19. 24 Dec, 2014 3 commits
  20. 20 Dec, 2014 1 commit
  21. 18 Dec, 2014 1 commit