Relevance: our build scripts make automated queries to GitHub. Historically, GitHub has allowed authentication using query parameters; both a user token and a client user/password pair could be specified as part of the URL. It now appears that this is being deprecated, per
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/ My research suggests that both styles (token and client-user/pwd) essentially consist in adding a line to the headers. In the case of an api token, it appears to be a line of the form Authorization: token <token-here> I’ve tested this one, and it appears to work. The other style of authentication (client auth) appears to use RFC 2617-style “basic” authentication. My reading of the RFC suggests that this essentially also consists of a request header line, of the form Authorization: Basic <base64-encoded-userid-and-password> … where the userid and password are appended with a colon and the base64 encoded (and yes, everything breaks if you have a colon in your userid). This one I haven’t implemented yet, I’m planning to come back when I need it (probably next week). In the meantime, though, I thought I’d ask whether you two (or any of the rest of you) have recently made this adaptation, and can tell me about terrible mistakes that I’ve already made or am about to make. Thanks! John -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/6f823d16-45f2-424d-bbc0-7c2ad11f04e7%40mtasv.net.
