stats.req.path may not be the real path requested about request-stats

[watson]

Hmm it seems that express is modifying req.url property 😞 Not the best move by express IMHO, so I'm not really sure if there's much I can do about it.

I could of course use req.originalUrl || req.url, but that seems oddly specific for this use-case. And I hate hacks like that. Preferably I'd like to make this more low-level.

How would you feel about just exposing the original request object, so that you can do stats.req.raw.originalUrl your self?

[dotchev]

Yes, this would be useful as the raw request may contain additional properties of statistical value.
To be consistent, you can expose also the raw response object.

[watson]

@dotchev this have now been released in v2.0.0 on npm