Jonas Finnemann Jensen

Or add a new option `rawHeaders` with type `Map`. I'm not sure there is an obvious fix..

IMO, the code would be cleaner using `shelf_router_generator`, but I guess that's a matter of taste. I think custom context could be attached using a handler that returns [routeNotFound](https://pub.dev/documentation/shelf_router/latest/shelf_router/Router/routeNotFound.html): ```...

You could also do: `router.put('/books', BooksController(context: {'reqtype': 'create'}));` Not sure why an untyped context is desirable. Closing this as shelf_router has moved, and I'm not sure this was necessary.

Are you sure it's not a different timeout?

Can you make a self-contained example.. maybe do `.timeout(const Duration(seconds: 30))` and see if you can reproduce reliably, and insert some `print` statements in `retryIf` to see what it called...

If anyone can demonstrate a trivial example and find a bug in retry I down for fixing it. But realistically I doubt much progress will be made on this issue....

No, plans this is not the purpose of this package. The package is for ensuring that some tasks runs periodically in a cloud environment. Where and how that task runs...

Let's first determine if we want this in `shelf_router`, then make a solution in `shelf_router_generator`. How is this different from using `Router.all`? And is not likely that we're going to...

I can see the point that allowing the `shelf_router.Route.mount` to wrap a `Handler` wouldn't be so bad :smile: Especially, when we already have the support in `shelf_router`, it wouldn't be...

No update, this is labeled as an enhancement. I don't think it's critical, if someone does I'm willing to help with code reviews. But as far as I'm aware nobody...