gorilla

I am using Go and the Gorilla web toolkit's mux and handler packages to build a complex application, part of which requires a http server. Gorilla's mux and handler packages work wonderfully and I am able to successfully get the http server up and running and it has been quite simple to log requests. However, I am unable to determine how I may log responses. Ideally, I would like a mechanism, similar to Gorilla's LoggingHandler, that "wraps" the logging mechanism easily. Is there a Golang package that does easily wraps / logs responses? Is there a way to use Go or Gorilla's capabilities in

I'm trying to implement Session handling and combine it with the go-endpoints package ! The package that i use to handle the session is Gorilla Sessions (github.com/gorilla/sessions), i would like some help.. I'm able to store a cookie to the client .. and when i call the endpoints is can see that the cookie is sent to the server. The problem while i try to get the Session values from the Session storage while the api is called, i cant get threw to the cookie .. it seams that the endpoints package strip the http.Request from extra content or something .. ? The place that i try to get the

In a go program, I want to run two web servers at the same time, obviously they will be serving on two different ports (and ip addresses if necessary), the problem is with the call to http.handle , when I try to register handler for '/' for the second server, it panics and says there is already a handler associated with '/', I guess I need to create a mux in addition to the DefaultServeMux and I tried to do it using the gorillaMux but couldn't figure it out, Is there something fundamentally wrong with running two web servers in the same program/process. To make it more clear, one of the two

I want to use Redis for session management. But I can't figure out what the advantage is of using Redis as a custom back-end for Gorilla sessions package over using it directly? link to the Gorilla session package: http://www.gorillatoolkit.org/pkg/sessions Gorilla sessions provides a means to wire up a storage system for session management provided you adhere to the interface provided. Currently, they give you two stores out of the box. One is a FilesystemStore that adheres to the interface that simply stores and retrieves session based data on the server's filesystem. The CookieStore as

I have an existing http server which I would like to profile. I have included _ "net/http/pprof" to my imports, and I already have http server running: router := createRouter() server := &http.Server { Addr: ":8080", Handler: router, ReadTimeout: 15*time.Second, WriteTimeout: 15*time.Second, // MaxHeaderBytes: 4096, } log.Fatal(server.ListenAndServe()) When I'm trying to access http://localhost:8080/debug/pprof/ I get 404 page not found . That's what I get when using go tool pprof on a local machine: userver@userver:~/Desktop/gotest$ go tool pprof http://192.168.0.27:8080/ Use of uninitialized

I'm using Go (Golang) 1.4.2 with Gorilla WebSockets behind an nginx 1.4.6 reverse proxy. My WebSockets are disconnecting after about a minute of having the page open. Same behavior occurs on Chrome and Firefox. At first, I had problems connecting the server and client with WebSockets. Then, I read that I needed to tweak my nginx configuration. This is what I have. server { listen 80; server_name example.com; proxy_pass_header Server; location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forward-Proto $scheme; proxy_http_version 1.1; proxy_set

I am trying to pass my database object along to my handlers, instead of having a global object. But I don't know if this is possible, I'm using Gorilla Mux package, and I can see that it takes a closure as a second param. // https://github.com/gorilla/mux/blob/master/mux.go#L174 // HandleFunc registers a new route with a matcher for the URL path. // See Route.Path() and Route.HandlerFunc(). func (r *Router) HandleFunc(path string, f func(http.ResponseWriter, *http.Request)) *Route { return r.NewRoute().Path(path).HandlerFunc(f) } Which then defines the params i can use, ideally i would like to