Skip to content
Snippets Groups Projects
  1. May 23, 2019
    • deuce's avatar
      FCC no longer supports non-TLS HTTP requests. · bc9d9a81
      deuce authored
      bc9d9a81
    • rswindell's avatar
      When editing an existing file/message, use the current terminal screen width · ef0d8296
      rswindell authored
      for the word_wrap line length (not the default, 79 cols).
      ef0d8296
    • rswindell's avatar
      Issue a QWK-packet-received confirmation request after a successful download · 85dd8b01
      rswindell authored
      of a QWK packet (sending the received-file-length as a post parameter):
       http[s]://host/qwk.ssjs?received=<length>
      If the file size matches the user's QWK packet size, the local (server-side)
      QWK packet is deleted.
      Passing an empty string to HTTPRequest.Post() since it requires a data
      paramater. :-( Using Post rather than Get 'cause the chicken hath spake:
      "<echicken> I think POST is probably technically the more correct way to do it"
      85dd8b01
    • rswindell's avatar
      QWKnet client using HTTP[S] rather than FTP (experimental at this time). · 45ff2baa
      rswindell authored
      Open questions/issues:
      - How can we confirm the REP file was received successfully - before deleting
        our local file
      - We're reading entire REP and QWK packet contents into memory (JS variables)
        there's likely a better way
      45ff2baa
    • deuce's avatar
      Icon should not have an extension if it's not an absolute path. · d025a084
      deuce authored
      "Application" is not a registered category.
      Add TerminalEmulator and Dialup categories.
      d025a084
    • rswindell's avatar
      Increase MAX_POST_LEN from 1MB to 4MB (QWK REP packets can be > 1MB) - · a59fba4a
      rswindell authored
        I think that > 1MB post data is supported, but the http_request.post_data
        property won't be created if the length > MAX_POST_LEN. Perhaps would just
        store the post data in a file (uh, it already is?) and expose the filename to
        JS scripts? It'd be a lot cleaner than storing the data in a file and then
        reading (or mem-mapping) the file and then copying the contents into a JS
        property.
      
      Allow the JS http_request.post_data property to contain NULs.
      
      open_post_file() will now open the post file (and return the FILE*) even if
        session->req.post_data is NULL, it just won't try to write to the file if the
        post_data is NULL.
      
      mem-map the large post data files using XPMAP_WRITE (read/write) rather than
        XPMAP_READ (read-only) - without this change, this line in read_post_data()
        would cause an exception:
          session->req.post_data[session->req.post_len]=0;
        Now, we seem to have the potential of an off-by-one here (if the length
        mem-mapped is not post_len + 1), but that isn't happening. <shrug>
      
      Fixed a couple of FILE pointer/descriptor leaks if post_to_file() failed.
      
      Changed name of post data file to SBBS_POST.*.*.data (it's not necessarily
      html).
      
      So now, uploads > 1MB work, but questions remain:
      - wouldn't PUT be a more appropriate method (than POST) for file uploads?
      - how can we support post_data > MAX_POST_LEN (now 4MB) in JS?
      a59fba4a
  2. May 22, 2019
  3. May 20, 2019
  4. May 16, 2019
  5. May 15, 2019
  6. May 13, 2019
  7. May 11, 2019
  8. May 09, 2019
Loading