storm lynx
I'm currently receiving a callback with query parameters
like https://example.com?param=1234¶m2=432&parm3=789
at the end of my function I would like to return the user to https://example.com without the params. How would I be able to do this?
My HttpResponse return keeps the query params. I'm unsure how to purge them cleanly within a service.
hardy solstice
Using: https://docs.rs/actix-web-lab/latest/actix_web_lab/web/struct.Redirect.html#method.to
async handler() -> actix_web::Result<impl Responder> {
// ...
Ok(Redirect::to("/"))
}
Nice I see you are the dev on this crate.. I found this when searching for an answer.. but I assumed there was a way to do it natively within tooling of just vanilla actix web.. but it seems I must use this 3rd party crate?
I say 3rd party lightly.. just trying to understand actix-web is out of scope for facilitating redirects?
hardy solstice
this particular feature will be in the next version of actix web
though redirects are just 307 responses with a Location header
hardy solstice
https://docs.rs/actix-web-lab/latest/src/actix_web_lab/redirect.rs.html#133-150
this is all it does really, it's not hard to code yourself if youd rather not take the dependency on -lab yet
storm lynx
I'm using the dependency.. Tested it and it works.. I guess my question.. what other cool little magic utilities would make it where I would want to use this crate besides this redirect? Any other cool tidbits that are low hanging fruit?
i know this is an unrelated help question.. but let's say i have 2 arms of code within a service .. like
match queryparam {
None => Ok(HttpResponse::Ok().body(body))
Some(queryparam) => Ok(Redirect::to("/"))
}
how would I avoid mismatched types?
mismatched types
expected struct `HttpResponse`
found struct `Redirect`
quite possibly, here's the current line up of features in -lab in terms of popularity:
https://github.com/robjtede/actix-web-lab/discussions/7
storm lynx
quite possibly, here's the current line up of features in -lab in terms of popul...
nice some of these look great
hardy solstice
i know this is an unrelated help question.. but let's say i have 2 arms of code ...
yep, fair, two options:
match queryparam {
None => Ok(Either::Left(HttpResponse::Ok().body(body)))
Some(queryparam) => Ok(Either::Right(Redirect::to("/")))
}
2. https://docs.rs/actix-web/latest/actix_web/trait.Responder.html#tymethod.respond_to
match queryparam {
None => Ok(HttpResponse::Ok().body(body))
Some(queryparam) => Ok(Redirect::to("/").respond_to(&req))
}
actually 2 wont work very well for you, stick to 1.
storm lynx
option 1, is pretty much only binary left/right ? if for some reason i needed a third option would i need to do something else?
or would i have nested left/right's?
hardy solstice
nested eithers yea, but okay lets give a better answer for >2 variants
match option {
One => Ok(HttpResponse::Ok().body(body).map_into_boxed_body())
Two => Ok(Redirect::to("/").respond_to(&req).map_into_boxed_body())
Three => Ok(Json(foo).respond_to(&req).map_into_boxed_body())
}
it starts getting a bit wordy, but it's a language limitation
storm lynx
ahh .map_into_boxed_body() the secret equalizer i didn't know about
storm lynx
```rust
match option {
One => Ok(HttpResponse::Ok().body(body).map_into_boxe...
is the idea to just put req: HttpRequest, in the function argument list?
hardy solstice
yep