c.Env init

[sundarv85]

Hello,

From the threads "Envinit middleware" and "How to initialise c.Env"

I assume that we have to initialize the c.Env map. I don’t see the middleware or a make being called for c.Env. How is it accomplished in this default project.

[elcct]

Hi,

Examples in those two threads call c.Env from the wrong context. The correct way is explained in the first thread (check renderer middleware that uses c.Env in the right context).

goji by default uses RequestID middleware on top, that initializes c.Env.

https://github.com/zenazn/goji/blob/3ed4dab2289fc04f5b4f95af9edc43d14089a64b/default.go#L14

https://github.com/zenazn/goji/blob/master/web/middleware/request_id.go#L62

Default Project doesn't change the default middleware stack, that's why there is no need to check for c.Env.

I hope this helps.

Thanks,
elcct

[sundarv85]

Hi @elcct

Thanks. That helps.

Just to clarify, as long as we use Goji without changing its source, that would mean the RequestID Middleware will always be called for every request and hence we never need to check for c.Env.

However, the other two threads also don’t change the middleware layer, so I did not quite understand why you say they were accessing c.Env in the wrong context. Could it be that when these issues were raised the RequestID middleware was not part of Goji?

Thanks,
Sundar

[sundarv85]

Hi @elcct

I see that when we use goji.Serve() - it automatically includes DefaultMux - which contains the RequestID middleware and hence the c.Env is initialised.

When you use graceful.ListenAndServe() then the default mux is not included, which means you have to initialise the c.Env in one of your own middleware.