rudimentary github wrangling

curl.sh

[samth@loki:~ plt] curl -u 'samth:PASSWORD' --data '{"title":"the title"}' https://api.github.com/repos/samth/test-bugs/issues

gh.rkt

#lang at-exp racket

(require net/url net/base64 net/uri-codec (planet dherman/json))

;; http-authorization-header : string string -> string
(define (http-authorization-header username password)
  (let ([username-bytes (string->bytes/utf-8 username)]
        [password-bytes (string->bytes/utf-8 password)])
    (string-append
     "Authorization: Basic "
     (bytes->string/utf-8 
      (base64-encode 
       (bytes-append username-bytes #":" password-bytes) #"")))))

(define data ;; works
  (string->bytes/utf-8 (jsexpr->json (hash 'title "found a bug"))))


(define data1 ;; works
  @(compose string->bytes/utf-8 string-append){{"title":"found a bug","body":"you cannot be serious" }})
(define data2 ;; works
  @(compose string->bytes/utf-8 string-append){{"title":"found a bug","body":"you cannot be serious"}})
(define (go d)
  (port->string
   (post-pure-port
    (string->url "https://api.github.com/repos/samth/test-bugs/issues")
    d
    (list (http-authorization-header "samth" "PASSWD")))))

• Neither worked for me.
• The next step is to listen on a port and see the difference between the two. Either use racket or netcat (nc -l 9898).
• The problem is that the base64 string has a newline in its end. I regexp-replaced it away and both versions work.
• Matthew extended that recently, so there's an optional argument to base64-encode for the line separator.

Can you fork this gist with a version that works? And why does the base64 string affect the later newline?

Note for the future: current gist works.