>>22
Thanks for the info. I'll remain hopeful that the admin sees this at some point. In the meantime, I've been trying to understand how the mit-scheme httpio library handles outgoing get/post requests, and I've been confusing myself tremendously.
I wanted to try having the backend make a request to an external website, and incorporate the result into a page that it serves, but I'm finding that it doesn't directly support https requests.
I've successfully made requests to http pages, but not https pages. I'm using http-get and http-post. To do this I did have to modify http-client-request so that it uses the value of uri verbatim rather than constructing a new one. There's been some other small changes as I worked through this but I haven't kept track of them very well.
In http-client.scm:call-with-http-client-socket; port 80 is specified as the fallback value. I haven't bothered with uri-authority-port yet, but I have tried just changing the fallback to 443. This results in the program hanging upon execution of read-http-response in http-client-exchange.
Using port 443, the program is at least able to make it as far as completing write-http-request in http-client-exchange.
I haven't verified that write-http-request actually sent out the request, or that the website received it.
I'm not sure where to go from here. It seems that the hang takes place in read-line (or in the procedure it calls), but when I try to redefine read-line, it seems to lose scope of a procedure that it calls. That being optional-input-port, which is unbound when I check it in a repl.
I guess this isn't directly relevant to the thread, but I don't think it really warrants a thread of its own. Sorry about that. Maybe I should just have the server use curl.