On Jun 22, 2011, at 9:27 AM, Greg Hendershott wrote:
> ;; make-ports : url -> in-port x out-port
> (define (make-ports url proxy)
> (let ([port-number (if proxy
Thanks for pointing out that the comments are out of sync with the code :-)
[another story for Sam's arsenal]
_
At first I thought you meant users would need to set this parameter
each time. Then I looked on GitHub.com and found this:
;; make-ports : url -> in-port x out-port
(define (make-ports url proxy)
(let ([port-number (if proxy
(caddr proxy)
(or (url-po
25 minutes ago, Greg Hendershott wrote:
> I also agree.
>
> It should be a very simple change in url-unit.rkt. The last line of
> `make-ports' is where `tcp-connect' is hardwired: [...]
Yeah, that part isn't complicated, but it was tricky to get things to
conform to the same API it has now. I d
I also agree.
It should be a very simple change in url-unit.rkt. The last line of
`make-ports' is where `tcp-connect' is hardwired:
;; make-ports : url -> in-port x out-port
(define (make-ports url proxy)
(let ([port-number (if proxy
(caddr proxy)
(
2011/6/18 Jordan Schatz :
>> HTTPS support should *really*, *really* be in Racket out of the box,
>> so that "get-pure-port" and friends do the right thing whether it's
>> HTTP or HTTPS.
> I'd second that...
>
> I haven't gotten to it yet but I think serving HTTPS also requires
> jumping through so
On Sat, Jun 18, 2011 at 6:55 PM, Eric Hanchrow wrote:
> I've wrapped the thing into a PLaneT package at
> http://planet.racket-lang.org/display.ss?package=ssl-url.plt&owner=offby1.
>
> The documentation is mostly a placeholder; I'd appreciate suggestions
> for improvements.
Cool; do you have a g
I've wrapped the thing into a PLaneT package at
http://planet.racket-lang.org/display.ss?package=ssl-url.plt&owner=offby1.
The documentation is mostly a placeholder; I'd appreciate suggestions
for improvements.
_
For list-related administrative tas
Jordan Schatz wrote at 06/18/2011 05:05 PM:
Anyway HTTPS is something I have to deal with all the time in my work as
a web developer and I think it would help people's perception of racket
as a professional web dev language if it was more out of the box.
Agreed.
FWIW, HTTPS is used heavily
> HTTPS support should *really*, *really* be in Racket out of the box,
> so that "get-pure-port" and friends do the right thing whether it's
> HTTP or HTTPS.
I'd second that...
I haven't gotten to it yet but I think serving HTTPS also requires
jumping through some hoops?
Anyway HTTPS is something
Sam Tobin-Hochstadt wrote at 06/18/2011 04:30 PM:
I've put all of these examples up on the GitHub Racket wiki:
https://github.com/plt/racket/wiki/HTTP-over-SSL
Hopefully, that will be a useful reference the next time someone asks about SSL.
HTTPS support should *really*, *really* be in Ra
I've put all of these examples up on the GitHub Racket wiki:
https://github.com/plt/racket/wiki/HTTP-over-SSL
Hopefully, that will be a useful reference the next time someone asks about SSL.
On Sat, Jun 18, 2011 at 11:39 AM, YC wrote:
> You can also try bzlib/http on planet - it can work with
You can also try bzlib/http on planet - it can work with SSL via the
following call:
(require (planet bzlib/http/client))
(http-get )
(http-post )
Hope this helps.
yc
On Sat, Jun 18, 2011 at 8:05 AM, Matthias Felleisen wrote:
> I have modernized the language (not really necessary) and adap
I have modernized the language (not really necessary) and adapted
the example so that it does something useful (not very) with a real https
url. See below. It's all in one drracket buffer to make it more
easily readable. I am sure you can split it up into separate files.
Basically all exports d
I am still pretty new to Racket, I've built a few trivial projects and am
now jumping into a more serious app. One of the first things I need to be
able to do though is work with (as a client, not server) https urls. GET
PUT POST HEAD DELETE, and most of the time send special headers.
I have seen
14 matches
Mail list logo
