HTTP servers

Question 1

Processing HTTP requests with Go is primarily about which two things?

Answer 1

Handlers & Servemuxes

Question 2

What are handlers fairly analogous to in MVC?

Answer 2

Controllers

Question 3

Generally speaking, what are handlers responsible?

Answer 3

Carrying out your application logic and writing response headers and bodies.

Question 4

What is a servemux also known as?

Answer 4

Router

Question 5

What does a servemux store?

Answer 5

A mapping between the predefined URL paths for your application and the corresponding handlers.

Question 6

How many servemuxes do you usually have?

Answer 6

One, containing all your routes

Question 7

Which Go package ships with the simple but effective http.ServeMux servemux?

Answer 7

net/http

Question 8

Which servemux is available from the net/http package?

Answer 8

http.ServeMux

Question 9

The net/http package has functions to generate common handlers. Give 3 examples.

Answer 9

http.FileServer(), http.NotFoundHandler() and http.RedirectHandler().

Question 10

Which function creates an empty servemux?

Answer 10

http.NewServeMux

Question 11

What parameters does http.NewServeMux take?

Answer 11

None e.g. mux := http.NewServeMux()

Question 12

How would you create a handler which 307 redirects all requests it receives to http://example.org?

Answer 12

rh := http.RedirectHandler(“http://example.org”, 307)

Question 13

How would you register a handler, rh, for all incoming requests with the URL path /foo?

Answer 13

mux.Handle(“/foo”, rh)

Question 14

What does the http.ListenAndServefunction do?

Answer 14

Creates a new server and starts listening for incoming requests

Question 15

What parameters does the http.ListenAndServe function take?

Answer 15

A port specification and a reference to our servemux e.g. http.ListenAndServe(“:3000”, mux)