

Is itĪs for having a different shutdown URL. I'm not sure why curl and the Web browser behave differently. How does the DrRacket "Stop" button stop a running web server nicely? I tried doing (break-thread (current-thread)) in the handler for /shutdown, but that didn't quit work either.įrom jay.mccarthy at Wed Jun 23 16:33:12 2010įrom: jay.mccarthy at (Jay McCarthy) " but this, like with curl, returns the "Server Stopped" page but doesn't actually stop the server.

I was playing around putting in a request to "/quit" in the handler for the /shutdown URL: "(get-pure-port (string->url ". suppose I want to set up a "/shutdown" URL that determines first if the current user is properly authenticated, and then shuts down the server.

In general, is there a good way to set up a different URL to stop the server? E.g. Here's the log file for the servlet (the two requests look identical):ġ27.0.0.1 - "GET /quit HTTP/1.1" 200 512Ģ. Now if I visit the same url in a browser, it stops after displaying the same HTML above.
