Jeb Rosen

Ah - thanks for that clarification.

It depends on when exactly the 400 is being returned. Is the 400 status code the one returned from Instagram, or did the `TokenRequest` guard fail and indicate a 400...

> `Warning: OAuth2 token exchange failed: token exchange returned non-success status code: 400` Yeah, in this case it's Instagram responding with 400. I think you've actually stumbled on a long-unimplemented...

I believe I ran into a related/similar issue. In my case, the underlying problem was that `locale-gen` was trying to run `gzip` to extract `UTF-8.gz`, but `gzip` wasn't initially installed....

I've gone back and forth on this quite a bit. On the one hand `FromParam` to me "feels like" it should mainly or only be used for quick validation and...

> so allowing the request guard to access the parameters (like they can access other guards) seems a good solution to me? I am, however, not sure if this is...

> Is it feasable to make that fragile solution less fragile? Using the index is certainly not robust enough. In principle it's not only feasible, it should be relatively trivial...

We log "Outcome: Forward" before trying the next route if a request guard returns `Outcome::Forward`. I like the idea of adding similar logging for routes that mismatch for reasons other...

@jhpratt you may be interested in [jebrosen/rocket_oauth2](https://github.com/jebrosen/rocket_oauth2). I wouldn't call it production-ready for several reasons and it is oauth-specific, but its model (good and bad) may serve as inspiration for...

> and it works when I test it with postman. As far as I know the `@filename` syntax is a feature of `curl`, and it's used to distinguish a file...