Add requestid to context

[rafiramadhana]

This PR is a proof of concept. So, it is very open for discussions.

Resolves #22

Add requestid to context, so we will have unique identifier for each request.

As starter, we are implementing it in KeyHandler.Create

[rafiramadhana]

Here, we are adding the request ID into incoming context (r.Context()).

The process is abstracted by chi's chiMiddleware.RequestID.

[rafiramadhana]

Here, we are getting the context with chiMiddleware.GetReqID.

Again, the process is abstracted by chi.

[joseph0x45]

Nice, this was simpler than I thought it would be

[joseph0x45]

Also one thing that I meant by

This middleware should only log requests either coming from the Frontend or authenticated requests going to the API.

is that, when I originally hosted the first version of Visio on a linode instance, I used Chi's logger middleware but my logs were bloated because of bot requests coming to the server. So I think passing an id down to the middlewares part can be handled by Chi, but we need another middleware that could tell if a request is coming either from our frontend or from a user, a very simple way I think we can solve this is by having a special value that would be passed in a special header in all requests coming from the frontend and as for the requests going to the API itself we could just check for the existence of the x-api-key header and reject the request if it is not set. Do you think it's a good approach?

[rafiramadhana]

Also one thing that I meant by

This middleware should only log requests either coming from the Frontend or authenticated requests going to the API.

is that, when I originally hosted the first version of Visio on a linode instance, I used Chi's logger middleware but my logs were bloated because of bot requests coming to the server. So I think passing an id down to the middlewares part can be handled by Chi, but we need another middleware that could tell if a request is coming either from our frontend or from a user, a very simple way I think we can solve this is by having a special value that would be passed in a special header in all requests coming from the frontend and as for the requests going to the API itself we could just check for the existence of the x-api-key header and reject the request if it is not set. Do you think it's a good approach?

i think that's a good idea

in addition, if the bots exhaust your server (i.e. our server processes bots' requests and returns HTTP 200 OK) we can also do rate limitting

[joseph0x45]

yep, rate limiting is definitely something I want to implement :)