1. 10 Feb, 2015 3 commits
    • 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.
    • Philipp Schafft's avatar
      Sync common/ · 9cf6d931
      Philipp Schafft authored
  2. 09 Feb, 2015 4 commits
  3. 07 Feb, 2015 1 commit
  4. 06 Feb, 2015 1 commit
  5. 02 Feb, 2015 5 commits
  6. 01 Feb, 2015 3 commits
  7. 25 Jan, 2015 2 commits
  8. 18 Jan, 2015 4 commits
  9. 16 Jan, 2015 2 commits
  10. 13 Jan, 2015 4 commits
    • Philipp Schafft's avatar
    • Philipp Schafft's avatar
      Cleanup: more cleanly define blocks for admin command IDs · 3b4e3ed0
      Philipp Schafft authored
      This adds info to the blocks about their size.
      Also added two more blocks:
      * for experimental features such as in private branches or
        or feature branches. This is for command IDs that are going to
        be merged with master some day. At merge they need to be changed
        and put into the regular position.
      * for private features that are not going to be merged into master.
        e.g. specific features for a very specific user that are not
        useful for general audiance.
      This should help keeping stuff sorted and largey reducing the risk
      of command ID collissions on merges of branches.
      Also this should make the merger's job a little bit more easy as
      there are less likely any conflicts on merge if someone else got
      a number closeby and those change is within the diff's context lines.
    • Thomas B. Rücker's avatar
      <!-- --> · 0a13b88a
      Thomas B. Rücker authored
    • Thomas B. Rücker's avatar
  11. 11 Jan, 2015 2 commits
  12. 10 Jan, 2015 2 commits
  13. 08 Jan, 2015 2 commits
  14. 06 Jan, 2015 2 commits
  15. 05 Jan, 2015 1 commit
  16. 31 Dec, 2014 2 commits