1. 29 Jun, 2019 10 commits
  2. 28 Jun, 2019 9 commits
  3. 23 Jun, 2019 1 commit
  4. 22 Jun, 2019 6 commits
    • rswindell's avatar
      Cosmetic improvments: · ae3c34f6
      rswindell authored
      Use "save/restore" uifc.list() mode for "Save Changes" prompt - no need to
      leave the prompt visible while saving changes.
      Display pop status while saving changes to config file.
    • rswindell's avatar
      Cosmetic fixes: · 061755f9
      rswindell authored
      Copy/paste errors from 2002 (changes -> uifc.changes in the help text).
      Use "save/restore" uifc.list() mode, rather than "remain active" for
      "Save Changes" prompt - no need to leave the prompt visible while saving
    • rswindell's avatar
      Bug-fix: Support [node:<addr>@<domain>] sections in AreaFix changes. · cae53945
      rswindell authored
      When processing area manager netmail messages, SBBSecho can modify
      (add/change) keys in the [node:*] section of the sbbsecho.ini file. Although
      SBBSecho would read node sections that had a domain (e.g. 5D address) just fine
      when processing area manager changes and writing those changes back to the
      sbbsecho.ini, only 4D addresses (no "@domain") were used in the section naming.
      This could result in duplicate node sections being created in the sbbsecho.ini
      file (one with a "@domain", one without) and then "bad things" could happen
      (e.g. BinkP authentication failures, packet authentication failures, etc.).
      Now, when SBBSecho writes linked-node setting to the sbbsecho.ini, it first
      checks for the full 5D address of the node and if that section exists, modify
      it, otherwise fall-through to the 3D/4D address of the node for the sectoin
    • rswindell's avatar
      Fix warnings from GCC. · 8db2caa4
      rswindell authored
    • rswindell's avatar
      MIME-encoded headers (header field values with RFC 2047 "encoded-words") are · d96bb5d0
      rswindell authored
      getting kind of crazy common now and being employed even when totally
      unnecessary (e.g. encoding strings that contain just plain ASCII):
      - normalize message header fields, when possible
      - normalize UTF-8 encoded characters, when possible (e.g. special punctuation
      This allows text filters (e.g. subject.can, name.can) to work on MIME-encoded
      header fields and notifications about received e-mails are legible to humans.
      Encoded-words that contain actual non-ASCII/CP437 chars (e.g. foreign symbols,
      emojis) are left as encoded-words to be dealt with by whatever displays the
      message header.
      Special handling of folded normalized field values was necessary because
      "White space between adjacent 'encoded-word's is not displayed." (per RFC 2047)
    • rswindell's avatar
      Address error: · 04b0f8bc
      rswindell authored
      line 34: Error: can't open \sbbs\exec\undefined.js: No such file or directory
  5. 21 Jun, 2019 2 commits
    • deuce's avatar
      Fix handling of responses with no content. · b311c1c3
      deuce authored
      This introduces a new request field send_content which indicates if the
      content should be sent.  This covers various cases like HEAD responses
      where there's an entity, but no content is sent as well as 204, 304, and 1xx
      responses where there is not even an entity.
      writebuf() will now enforce this, so there's no need for various checks
      throughout the code to see if data should be sent or not.
      Also, we now only set sent_headers after the headers are sent.
    • deuce's avatar
      Some RFC nits. · c50acc36
      deuce authored
      1) Send Content-Length even if we will be closing the connection.
      2) Send the highest HTTP version in the status line that has the same major version.
  6. 20 Jun, 2019 5 commits
  7. 17 Jun, 2019 2 commits
  8. 15 Jun, 2019 5 commits