You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'd like to be able to log out the query parameters of a request, to aid in development of a webserver where I'd like to see what query parameters a blackbox client is sending up.
Describe the solution you'd like
A way to have the query parameters in log output, like so:
Is your feature request related to a problem? Please describe.
I'd like to be able to log out the query parameters of a request, to aid in development of a webserver where I'd like to see what query parameters a blackbox client is sending up.
Describe the solution you'd like
A way to have the query parameters in log output, like so:
Describe
alternativesideas you've consideredI'd like to expose
Route::query
on log'sInfo
struct, perhaps as two methods:pub fn query_params(&self) -> &str
returns?x=1&y=2
(possibly returning
String
if the&str
isn't available)pub fn path_with_query(&self) -> &str
returns/api/whatever?x=1&y=2
(same)
warp::log::with_query
to do this automatically, alongsidewarp::log
.If these ideas aren't too controversial, I'm happy to make a PR for them.
The text was updated successfully, but these errors were encountered: