RFC 7231 Section 6.5.5

States that

The origin server MUST generate an
Allow header field in a 405 response containing a list of the target
resource's currently supported methods.

Which is clearly not implemented right now
https://github.com/gorilla/mux/blob/75dcda0896e109a2a22c9315bca3bb21b87b2ba5/mux.go#L601-L603

Sugg

Points to cover

• An application can handle subprotocol negotiation on its own by setting the Sec-Websocket-Protocol response header. The Subprotocols(r *http.Request) []string function is helpful here.
• Set u.Subprotocols for builtin subprotocol negotiation. Builtin negotiation overrides a subprotocol specified in the response header (it would have been better to return an error, but it

Is there a reaper for the FilesystemStore that deletes stale sessions at a regular interval?
An example would be boltstore reaper created here. Is this really necessary?

Is your feature request related to a problem? Please describe.
We are using recovery handler with stack trace. However, as per https://github.com/gorilla/handlers/blob/master/recovery.go#L89, stack trace is only printed to stdout.

Describe the solution you'd like
As we are logging everything as json, having raw stdout for stack trace is not ideal. It will be great to have ability to p

Currently, sessions are stored in the application memory. Adding a memcached driver will let developers share sessions across app instances