Add middleware support as discussed in #293 #294

nadiamoe · 2017-09-11T16:13:05Z

See discussion in #293 for more details.

nadiamoe · 2017-11-06T12:02:32Z

Status update: I've rebased middleware branch to match latest version of master. Now middlewares are not executed if a not found or method mismatch event occurs, even if custom handlers are used. I've added test cases for these, and improved some existing ones.

As this commit list is getting huge, I'll squash them after you review individual changes.

elithrar · 2017-11-07T03:39:16Z

README.md

+### Middleware
+
+
+Since **vX.Y.Z**, mux supports the addition of middlewares to a router, which are executed if a


Replace "router" with [Router](https://godoc.org/github.com/gorilla/mux#Router) so that we link to the docs.

elithrar · 2017-11-07T03:39:43Z

README.md

+
+
+Since **vX.Y.Z**, mux supports the addition of middlewares to a router, which are executed if a
+match is found (including subrouters). Middlewares are defined using the de facto standard function:


s/function/type

elithrar · 2017-11-07T03:40:11Z

README.md

+func(http.Handler) http.Handler
+```
+
+Structs that implement the `Middleware` interface can also be used:


s/Structs/Types

elithrar · 2017-11-07T03:40:58Z

README.md

+}
+```
+
+Middlewares can be added to a router using `Router.AddMiddlewareFunc()` and


Examples for both please!

elithrar · 2017-11-07T03:43:56Z

README.md

+Structs that implement the `Middleware` interface can also be used:
+
+```go
+type Middleware interface {


I'm not entirely convinced this interface is useful. Can you expand more on how this is a better API vs. only supporting func(http.Handler) http.Handler - ?

nadiamoe · 2017-11-07T09:45:21Z

Thanks for the comments. You're right about the docs, its a bit lacking. Middleware interface is useful for building complex middlewares which need to hold some data and/or extra logic. Also it gives the API some parallelism with http.Handler and http.HandlerFunc: Same concept, but in different places. Other routers and middleware managers use the same strategy, as it is a simple way to keep complex middlewares tidy and clean.

I'll add extra examples and fix the issues you pointed out over the course of this week, I'll be pretty busy at work until Wed :(

nadiamoe · 2017-11-09T11:03:32Z

I've fixed some of the issues you pointed out in the commit above. Please tell me if there are something else which needs improvement.

elithrar · 2017-11-10T04:23:18Z

Also it gives the API some parallelism with http.Handler and http.HandlerFunc: Same concept, but in different places. Other routers and middleware managers use the same strategy, as it is a simple way to keep complex middlewares tidy and clean.

Do you have examples? I'm partial to chi, which has a Use((http.Handler) http.Handler) method on the router, but the concept of a Middleware interface seems less common.

For context: adding two methods is 100% more decision-making that a package user has to make, and adds to our already extensive package API. Thus, I'm pushing hard for utmost simplicity unless there's a clear case where the interface-based support makes sense. I can't see that it makes sense right now.

nadiamoe · 2017-11-10T10:36:41Z

There is an example on https://github.com/roobre/gorilla-mux/blob/middleware/README.md#middleware, line 427:

// Define our struct
type authenticationMiddleware struct {
	tokenUsers map[string]string
}

// Initialize it somewhere
func (amw *authenticationMiddleware) Populate() {
	amw.tokenUsers["00000000"] = "user0"
	amw.tokenUsers["aaaaaaaa"] = "userA"
	amw.tokenUsers["05f717e5"] = "randomUser"
	amw.tokenUsers["deadbeef"] = "user0"
}

// Middleware function, which will be called for each request
func (amw *authenticationMiddleware) Middleware(next http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        token := r.Header.Get("X-Session-Token")
        
        if user, found := amw.tokenUsers[token]; found {
        	// We found the token in our map
        	log.Printf("Authenticated user %s\n", user)
        	next.ServeHTTP(w, r)
        } else {
        	http.Error(w, "Forbidden", 403)
        }
    })
}

r := mux.NewRouter()
r.HandleFunc("/", handler)

amw := authenticationMiddleware{}
amw.Populate()

r.AddMiddleware(&amw)

Without implementing this interface, instead of mux.AddMiddleware(authenticator) we would have to write mux.AddMiddlewareFunc(authenticator.Middleware), which seems a bit clunkier to me.

It's just the same as http.Handler. Go devs could have left the API without the Handler interface and everything would work the same, but instead of http.ListenAndServe(":8000", mux) we would have to write http.ListenAndServe(":8000", mux.ServeHTTP).

The extra decision making is indeed here, but it is for a reason: You either want a simple middleware which, for example, logs requests, or a complex one which can hold data structures, have extra logic, etc. Just like it happens with handlers.

The Middleware interface helps code reusability too, as having a middleware interface kind of forces users to name their middleware methods all the same, so they can be exchanged with ease. Let try to give an example: Let's suppose my logger middleware becomes extremely popular, and I decide to give it a separate package: roob.re/loggermiddleware. A potential user which already have another middleware, let's say, randomRejectMiddleware, wants to add it to their stack:

package main

import (
    "net/http"
    "github.com/gorilla/mux"
    "roob.re/loggermiddleware"
)

// [...]

func main() {
    mux := mux.NewRouter()

    rrmw := &randomRejectMiddleware{}
    lgmw := loggermiddleware.New(log)

    mux.AddMiddleware(rrmw)
    mux.AddMiddleware(lgmw)

    // [...]
}

This looks simple enough. Without the middleware interface, we could have called our Middleware(http.Handler) http.Handler function different, and it would probably look like:

package main

import (
    "net/http"
    "github.com/gorilla/mux"
    "roob.re/loggermiddleware"
)

// [...]

func main() {
    mux := mux.NewRouter()

    rrmw := &randomRejectMiddleware{}
    lgmw := loggermiddleware.New(log)

    mux.AddMiddleware(rrmw.DoMiddleware)
    mux.AddMiddleware(lgmw.MiddlewareLogic)

    // [...]
}

I know the names are quite absurd, but you get the point. The middleware interface forces an standard middleware writes can adhere to, and makes the code to add them look simpler and nicer. Just like http.Handler does.

advdv · 2017-11-18T19:49:50Z

Any progress on this? Would love to use this for a new project ;)

elithrar · 2017-11-18T20:00:22Z

Still needs review, and I’m just getting back from vacation. Soon!

…

On Sat, Nov 18, 2017 at 2:49 PM Ad van der Veer ***@***.***> wrote: Any progress on this? Would love to use this for a new project ;) — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#294 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABIcH6mB6pICNIIx3a5cqCiw0s7sdS1ks5s3zTfgaJpZM4PTaEY> .

xgfone · 2017-12-10T15:27:08Z

I like this feature, too!

abdullah2993 · 2017-12-11T06:42:05Z

any status update so far?

elithrar

Minor changes. Let's start with a smaller API for this first. I'm otherwise happy with the tests + impl.

elithrar · 2017-12-11T06:45:38Z

middleware.go

+
+import "net/http"
+
+type Middleware interface {


I don't think we should keep this. Single method interfaces can be restrictive; best to let the package user define a wrapper if needed. We end up adding similarly-named methods to the API.

(if there is demand over time, we can re-assess)

I still think that adding the Middleware interface will help to keep middlewares more standard, and the parallelism with net/http Handler and HandlerFunc helps users to understand the behaviour. This pattern is also seen in other routers and middleware managers (see negroni, for example).

However, if you think it doesn't fit the project, I'll remove it.

elithrar · 2017-12-11T06:46:40Z

doc.go

+		})
+	}
+
+Note: The handler chain will be stopped if your middleware doesn't call `next.ServeHTTP()`


We should document/clarify how handlers are executed (in order they added).

Roger, I'll clarify the calling order and stopping condition.

elithrar · 2017-12-11T06:48:13Z

@kisielk - let me know if you echo my thoughts here.

nadiamoe · 2017-12-11T12:59:28Z

I'll address the changes listed above when I return from vacation. I'm sorry for the inconvenience :(

Btw, I'll probably rebase master and squash some (or all) of the PR commits, as the list seems to be getting too big.

elithrar · 2017-12-11T13:33:42Z

No inconvenience at all!

…

On Mon, Dec 11, 2017 at 4:59 AM Roberto Santalla ***@***.***> wrote: I'll address the changes listed above when I return from vacation. I'm sorry for the inconvenience :( — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#294 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABIcF9qAba43ejVIg0EZcDxPGXHhsZMks5s_ScwgaJpZM4PTaEY> .

elithrar · 2017-12-28T16:54:18Z

@roobre - let me know if you need any help here. Would love to help get this merged in! 🙌🏼

nadiamoe · 2017-12-30T00:51:06Z

Sorry, I'm on vacation until maybe 3-4 Jan, so I've been quite inactive here :_

I'll get this rebased and fixed as soon as I get home. But I'd like to see if you have reached a consensus about the Middleware interface (basically if I should remove it or not) (/cc @kisielk)

kisielk · 2017-12-30T01:18:18Z

Hm, I'm not sure how I feel about the interface. What would the alternative look like?

elithrar · 2017-12-30T20:49:00Z

@kisielk

Without the interface, we should just have (as the public API):

// Takes a func (http.Handler) http.Handler
route.AddMiddleware(mw)

The interface we rally around is http.Handler rather than anything else.

There may be *some desire for a http.HandlerFunc option -

// Takes a func (http.HandlerFunc) http.HandlerFunc
router.AddMiddlewareFunc(mw)

... but I'd rather tease that out by starting minimally.

kisielk · 2018-01-03T18:55:42Z

Ah I understand now. Yes I think just using func (http.Handler) http.Handler as a type for the middleware is just fine. No need to make everything into an interface that you need to implement. A much less "object-oriented" approach and more a functional transformation.

nadiamoe · 2018-01-03T22:38:11Z

@kisielk It's not exactly as you said. The interface just wraps func (http.Handler) http.Handler as a receiver and gives it a name. Just like http.Handler does with http.HandlerFunc. You can see a detailed explanation above: #294 (comment)

kisielk · 2018-01-03T22:45:59Z

Yeah, I understand that, but having the MiddleWare method on the type is unnecessary.

// Define our struct
var tokenUsers :=  map[string]string{
	"00000000": "user0",
	"aaaaaaaa": "userA",
	"05f717e5": "randomUser",
	"deadbeef": "user0",
}

// Middleware function, which will be called for each request
func AwmMiddleware(next http.Handler) http.Handler {
    return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        token := r.Header.Get("X-Session-Token")
        
        if user, found := tokenUsers[token]; found {
        	// We found the token in our map
        	log.Printf("Authenticated user %s\n", user)
        	next.ServeHTTP(w, r)
        } else {
        	http.Error(w, "Forbidden", 403)
        }
    })
}

Then you don't need to create additional type boilerplate. At this point the interface would be created solely for the purpose of calling one method on Mux, which seems like it's unnecessary.

ckeyer · 2018-01-04T15:26:17Z

like

nadiamoe · 2018-01-10T10:38:37Z

Rebased to latest commits on master.

Note: I've also squashed the whole history to make rebase easier from now (it started giving conflicts on re-edited files and it is a bit of a pain).

Middleware now uses de facto implementation Signed-off-by: Roberto Santalla <roobre@roobre.es> Middlewares are now executed in the same order they're added Signed-off-by: Roberto Santalla <roobre@roobre.es> Moved middleware chain build process from ServeHTTP() to Match() This allows middleware to be executed even when it's not Router who calls the handler directly (e.g. subrouters) Signed-off-by: Roberto Santalla <roobre@roobre.es> Added some tests for middleware functionality go < 1.6 doesn't like http.Method* constants Added more tests to check if middleware is executed correctly Added middleware documentation Added check to execute middleware only if no errors were found Fixed middleware test for custom 404 handler Added middleware tests for subrouters, improve and reorder existing ones Improved docs on README mux.Middleware type is now private (mux.middleware) Rewritten README.md docs, added a few more comments to middleware.go Added Middleware section to index

elithrar · 2018-01-10T13:47:03Z

Good to review?

…

On Wed, Jan 10, 2018 at 2:38 AM Roberto Santalla ***@***.***> wrote: Rebased to latest commits on master. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#294 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABIcB5KHrRtnDw4V6yspm9PjzjlKu1Oks5tJJMugaJpZM4PTaEY> .

elithrar

LGTM: almost there @roobre! Just some doc changes and a method naming recommendation.

elithrar · 2018-01-10T15:46:53Z

README.md

@@ -447,6 +448,82 @@ func main() {
 }
 ```

+### Middleware
+


Add a quick paragraph describing what middleware is / what it can be used for, and link to https://github.com/gorilla/handlers

Version will be v1.6.1 if we merge this week (I'll cut a new release after this PR is merged in)

e.g.

Middleware describes intermediate handlers that can check, mutate or log the incoming request or outgoing response. mux makes it easy to add middleware to a Router or Subrouter...

Btw, I forgot to mention I did not add the link because most handler don't actually implement mux.Middleware, as they require additional parameters. We could circunvent this using closures, but I think it would confuse some users instead of adding clarity. Maybe we could rework some handlers to make them comply with the interface?

Maybe instead of changing them we could add a XXXXMiddleware function for each one?

Yes, of course. We should not break existing handlers, so maybe wrapping them somehow, or refactoring the core logic into a different, private function and exposing both the actual and the Middleware flavours of it. I can give it a shot if you think it's worth it.

elithrar · 2018-01-10T15:48:56Z

README.md

+r.AddMiddlewareFunc(amw.Middleware)
+```
+
+Note: The handler chain will be stopped if your middleware doesn't call `next.ServeHTTP()` with the corresponding parameters. This can be used to abort a request if the middleware writer wants to.


"This can be used to avoid passing the request on, but make sure to return a response to the client from within the middleware"

Note: a library of useful logging, CORS and proxy-related middleware can be found in the gorilla/handlers package

Added, but reworded "make sure" to "should", as some particular scenarios may apply and it is not a mux requirement.

elithrar · 2018-01-10T15:49:15Z

doc.go

@@ -238,5 +238,70 @@ as well:
 	url, err := r.Get("article").URL("subdomain", "news",
 	                                 "category", "technology",
 	                                 "id", "42")
+
+Since **vX.Y.Z**, mux supports the addition of middlewares to a [Router](https://godoc.org/github.com/gorilla/mux#Router), which are executed if a


Update to align with the README

(Note to self: use tooling to make this automatic...)

I removed the version thingie. I'm not sure if its an important enough information to be in the readme. Feel free to re-add it if you think it is.

Good move. I think it's fair to assume that the documentation reflects HEAD.

Hi there. I can see that the online documentation has the *vX.Y.Z*. Also the link [Router](...) hasn't been converted to HTML.

Yikes, I totally missed that one :/
I can fix it and create a new PR if you want, but maybe you can edit it quicker @elithrar

I’ll take a look today. The website doesn’t do Markdown, which is a bit of a pain.

Cool, thanks guys :)

elithrar · 2018-01-10T15:51:21Z

middleware.go

+	Middleware(handler http.Handler) http.Handler
+}
+
+// MiddlewareFunc also implements the Middleware interface.


Update this? As we don't export the Middleware interface (middleware) this may be confusing.

Do you mean the comment or the implementation?

The implementation needs to be there in order to store MiddlewareFunc as Middleware in the middlewares slice. But the comment needs to be updated indeed, I slipped there :P

Just the comment 👌🏼

elithrar · 2018-01-10T15:56:22Z

middleware.go

+}
+
+// AddMiddlewareFunc appends a MiddlewareFunc to the chain.
+func (r *Router) AddMiddlewareFunc(mwf MiddlewareFunc) {


AddMiddleware, Add or UseMiddleware or just Use might be less verbose here.

chi and echo call their methods Use

express also calls it use

Downside to Use - not entirely self-documenting.

I'd be OK with just calling this function Middleware as "Add" is obvious, and subtracting it/removing it later is (mostly) a non-option.

I don't like the AddMiddlewareFunc name either, seems way too long to me. But I think we should keep the "func" part somewhere, as it makes what this function expects very clear, and avoids the need for a breaking change if the middleware interface is exported in the future.

What about UseFunc?

Let’s just stick with Use - as that’s familiar and aligns with the Handle (takes a http.Handler) and HandleFunc (takes a HandlerFunc) on Router. This somewhat sits in the middle, but familiarity wins out in lieu of other objections.

Done. I've renamed the internal addMiddleware to useInterface, to avoid collision with Use.

elithrar · 2018-01-10T15:58:10Z

middleware.go

+func (mw MiddlewareFunc) Middleware(handler http.Handler) http.Handler {
+	return mw(handler)
+}
+


Middleware adds a middleware to the chain. Middleware can be used to intercept or otherwise modify requests and/or responses, and are executed in the order that they are applied to the Router.

nadiamoe · 2018-01-13T00:10:16Z

I'll patch this along the weekend, probably tomorrow.

to Use{Interface,} respectively

nadiamoe · 2018-01-16T16:11:50Z

Fixed most of the things, please tell me what you think :D

elithrar · 2018-01-16T16:17:14Z

OK - I'm going to test this in an application I have running (hopefully tonight) so we can get this merged.

Excited to land this.

@kisielk - if you can review in the interim that'd be great!

kisielk

Looks good other than some documentation nits.

kisielk · 2018-01-16T16:24:02Z

README.md

@@ -447,6 +448,86 @@ func main() {
 }
 ```

+### Middleware
+
+Mux supports the addition of middlewares to a [Router](https://godoc.org/github.com/gorilla/mux#Router), which are executed in the order they are added if a match is found (including subrouters).


IMO it's bad style to place so many sentence fragments in parentheses. It just adds unnecessary noise to the text and obfuscate the meaning. You can almost always restructure text to not use them. In this sentence you could say "router or subrouter" instead, or add another sentence here or later in the text that says "when a match is found the request is passed to the middleware in the current router and its parents".

kisielk · 2018-01-16T16:25:05Z

README.md

+### Middleware
+
+Mux supports the addition of middlewares to a [Router](https://godoc.org/github.com/gorilla/mux#Router), which are executed in the order they are added if a match is found (including subrouters).
+Middlewares are (typically) small pieces of code which take one request, do something with it (e.g. log some fields, add/remove some headers), and pass it down to another middleware or the final handler.


The (typically) is arguably one valid use of parentheses, but the examples could be another sentence to not interrupt the flow.

kisielk · 2018-01-16T16:26:07Z

README.md

+type MiddlewareFunc func(http.Handler) http.Handler
+```
+
+Typically, the returned handler is a closure which does something with the http.ResponseWriter and http.Request passed to it, and then calls the handler passed as parameter to the MiddlewareFunc (closures can access variables from the context where they are created).


Another use of parens that could be avoided.

nadiamoe · 2018-01-16T16:46:36Z

There you go, @kisielk. I appreciate feedback on these grammar mistakes, as I'm not a native speaker I sometimes slip things here and there :(

kisielk · 2018-01-16T16:48:28Z

That one is just something that stands out because it used to be a really bad habit of mine. I used to write stuff that had parentheses in nearly every sentence because that's just how my train of thought works. Then based on feedback I realized it doesn't necessarily make for the easiest reading for other people :)

nadiamoe · 2018-01-16T16:52:33Z

Same here, I usually think the main points while mentally adding small exceptions and clarifications here and there, so I tend to add parenthesis and clarifications everywhere instead of rewording the whole thingk and making it more linear. Anyway, as I said, I appreciate the feedback :D

elithrar · 2018-01-16T17:21:21Z

OK: sanity checked locally and all works as expected, esp. around Subrouters. I'm going to put this in prod soon to expose some heap & goroutine profiles behind authentication, so timing is good!

elithrar · 2018-01-16T17:24:22Z

Thanks for your work on this @roobre—appreciate your responsiveness and patience!

elithrar · 2018-01-16T17:30:20Z

Tagged in v1.6.1 - https://github.com/gorilla/mux/releases/tag/v1.6.1

iambudi · 2018-01-17T01:13:07Z

Trying to use middleware but i have this error message.
r.AddMiddleware undefined (type *mux.Router has no field or method AddMiddleware)

r := mux.NewRouter()
r.HandleFunc("/", handler)
r.AddMiddleware(myMiddleware)

kisielk · 2018-01-17T01:17:40Z

It should be r.Use(myMiddleware). Seems we forgot to adjust that one example in the docs.

kisielk · 2018-01-17T01:19:42Z

Updated the docs in 85e6bff, @elithrar should we tag a new release for the doc update?

iambudi · 2018-01-17T01:22:58Z

@kisielk Thanks. It works now.

elithrar · 2018-01-17T03:27:45Z

See #332 for the docs fix.

Addresses #294 (comment)

kgadams · 2018-02-01T10:25:36Z

Hi,
I love this feature, however I think you should clarify in the documentation if the middelware needs to be concurrency safe (I assume it does).
So the authenticationMiddleware only works if the amw.tokenUsers hash is never updated while the webserver is running. Otherwise you get nasty races.

nadiamoe · 2018-02-01T10:31:48Z

Middleware does indeed need to be thread-safe if it keeps state across requests, as go's http server spawns a new goroutine per request. Maybe I thought this was more obvious than it actually is, so writing it down may help some users. May I open a new PR clarificating it or do you guys prefer to handle this yourselves?

kgadams · 2018-02-01T11:02:29Z

Just go ahead, it's your baby :-)

elithrar self-assigned this Nov 7, 2017

elithrar added documentation enhancement needs review and removed documentation labels Nov 7, 2017

elithrar requested review from elithrar and kisielk November 7, 2017 03:38

elithrar suggested changes Nov 7, 2017

View reviewed changes

nadiamoe mentioned this pull request Nov 26, 2017

Subrouters match the wrong method when more than one matches #300

Closed

elithrar suggested changes Dec 11, 2017

View reviewed changes

elithrar suggested changes Jan 10, 2018

View reviewed changes

Improved docs and renamed AddMiddleware{,Func} functions

7a29b0c

to Use{Interface,} respectively

kisielk approved these changes Jan 16, 2018

View reviewed changes

Removed some parentheses

f799d21

elithrar approved these changes Jan 16, 2018

View reviewed changes

elithrar merged commit 53c1911 into gorilla:master Jan 16, 2018

elithrar mentioned this pull request Jan 17, 2018

PR for middleware support #293

Closed

elithrar added a commit that referenced this pull request Jan 18, 2018

[docs] Fix doc.go

5cebbc3

Addresses #294 (comment)

elithrar mentioned this pull request Jan 18, 2018

[docs] Fix doc.go #333

Merged

elithrar added a commit that referenced this pull request Jan 18, 2018

[docs] Fix doc.go (#333)

ad87908

Addresses #294 (comment)

		### Middleware


		Since vX.Y.Z, mux supports the addition of middlewares to a router, which are executed if a



		Since vX.Y.Z, mux supports the addition of middlewares to a router, which are executed if a
		match is found (including subrouters). Middlewares are defined using the de facto standard function:

Add middleware support as discussed in #293 #294

Add middleware support as discussed in #293 #294

Conversation

nadiamoe commented Sep 11, 2017

nadiamoe commented Nov 6, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nadiamoe commented Nov 7, 2017

nadiamoe commented Nov 9, 2017

elithrar commented Nov 10, 2017 • edited Loading

nadiamoe commented Nov 10, 2017

advdv commented Nov 18, 2017

elithrar commented Nov 18, 2017 via email

xgfone commented Dec 10, 2017

abdullah2993 commented Dec 11, 2017

elithrar left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

elithrar commented Dec 11, 2017

nadiamoe commented Dec 11, 2017 • edited Loading

elithrar commented Dec 11, 2017 via email

elithrar commented Dec 28, 2017

nadiamoe commented Dec 30, 2017 • edited Loading

kisielk commented Dec 30, 2017

elithrar commented Dec 30, 2017

kisielk commented Jan 3, 2018

nadiamoe commented Jan 3, 2018

kisielk commented Jan 3, 2018

ckeyer commented Jan 4, 2018

nadiamoe commented Jan 10, 2018 • edited Loading

elithrar commented Jan 10, 2018 via email

elithrar left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dgellow Jan 18, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nadiamoe commented Jan 13, 2018

nadiamoe commented Jan 16, 2018

elithrar commented Jan 16, 2018

kisielk left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nadiamoe commented Jan 16, 2018

kisielk commented Jan 16, 2018

nadiamoe commented Jan 16, 2018

elithrar commented Jan 16, 2018

elithrar commented Jan 16, 2018

elithrar commented Jan 16, 2018

iambudi commented Jan 17, 2018

kisielk commented Jan 17, 2018

elithrar commented Nov 10, 2017 •

edited

Loading

nadiamoe commented Dec 11, 2017 •

edited

Loading

nadiamoe commented Dec 30, 2017 •

edited

Loading

nadiamoe commented Jan 10, 2018 •

edited

Loading

dgellow Jan 18, 2018 •

edited

Loading

nadiamoe commented Feb 1, 2018 •

edited

Loading