This may be an OS question, but it manifested as a curious racket problem, so I thought I’d ask. Consider the following program:
#lang racket (require net/url) (post-impure-port (string->url "http://brinckerhoff.org:8025/";) #"request=1234" '("Content-Type: application/x-www-form-urlencoded”)) Basically, just open a connection to a web server. The observed and reproducible behavior when running in DrRacket 7.4.0.1 was that there was a 77-second delay, and then the port was opened just fine. Looking at the back end (this was a connection to a racket web server, perhaps unfortunately), there was no evidence of a connection until the 77 seconds was up. Contacting the given URL (http://brinckerhoff.org:8025/) with a web browser (Firefox), though, produced a near-instantaneous response—about 2 seconds. I saw the same delay when running the program using ‘racket’ at the command-line. I then rebooted my machine (MacOS Mojave 10.14.6). The problem went away. In retrospect, I regret rebooting before doing more experimentation; does this apply to other versions of Racket? Other ways of connecting? So, it looks like both DrRacket and Racket were experiencing some kind of persistent OS-related network block. All the (mumble)s were taken? But then, why did the web browser go through? Perhaps the web browser has some deeper knowledge of the OS that allows it to detect and work around this problem. Can anyone shed any light on whether this is a) a known issue with the operating system, b) a misunderstanding on my part, or b) a bug/problem with Racket? Many 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/838316e3-8897-40e1-a8a3-bc7b65d7fb84%40mtasv.net.
