It might be a good idea to handle HEAD exactly like GET as a default unless HEAD is supported specifically (i.e., HEAD /route should get mapped to the same handler as GET /route unless a specific head method is specified). GET should be idempotent content; HEAD normally returns the headers associated with a GET request, so that consumers can check to see if new content exists without the network cost of transferring the entire content.
It might be a good idea to handle HEAD exactly like GET as a default unless HEAD is supported specifically (i.e.,
HEAD /routeshould get mapped to the same handler asGET /routeunless a specific head method is specified). GET should be idempotent content; HEAD normally returns the headers associated with a GET request, so that consumers can check to see if new content exists without the network cost of transferring the entire content.