unexpected goroutine behaviour

this does work

package main
import (
  . "fmt"
  . "net/http"
)

const ADDRESS = ":1024"
const SECURE_ADDRESS = ":1025"

func main() {
  message := "hello world"
  HandleFunc("/hello", func(w ResponseWriter, r *Request) {
    w.Header().Set("Content-Type", "text/plain")
    Fprintf(w, message)
  })

  go func() {
    ListenAndServe(ADDRESS, nil)
  }()

  ListenAndServeTLS(SECURE_ADDRESS, "cert.pem", "key.pem", nil)
}

this doesn't work

package main
import (
  . "fmt"
  . "net/http"
)

const ADDRESS = ":1024"
const SECURE_ADDRESS = ":1025"

func main() {
  message := "hello world"
  HandleFunc("/hello", func(w ResponseWriter, r *Request) {
    w.Header().Set("Content-Type", "text/plain")
    Fprintf(w, message)
  })

  go func() {
    ListenAndServe(ADDRESS, nil)
  }()

  go func() {
    ListenAndServeTLS(SECURE_ADDRESS, "cert.pem", "key.pem", nil)
  }()

  for {}
}

I'd expect the for{} to block and the goroutines to launch successfully, but that doesn't appear to happen on OSX 10.9.3.

You could use a sync.WaitGroup, but what version of go are you using?:

var wg sync.WaitGroup
wg.Add(2)
go func() {
    ListenAndServe(ADDRESS, nil)
    wg.Done()
}()

go func() {
    ListenAndServeTLS(SECURE_ADDRESS, "cert.pem", "key.pem", nil)
    wg.Done
}()

wg.Wait()

does runtime.GOMAXPROCS(2) make the 2nd example work for you?