#[post(\n \"/api/user/<username>/events/authorize\",\n format = \"application/activity+json\",\n data = \"<authorization>\"\n)]#[get(\"/.well-known/host-meta\", format = \"application/xrd+xml\")]And so forth. These are all well-known types (except for maybe application/activity+json which seems to be newer), but they aren't known to Rocket. I've dug through https://api.rocket.rs/v0.5-rc/rocket/http/struct.ContentType.html looking for ways to define them manually, but can't figure out how I would enable the post and get macros to use those. It's mostly an aesthetics thing since the manually specified unknown types work - the IDE just complains about it and I don't see a way to tell it to ignore it (and I'd also just like it to be right).
Also, is there a way to use multiple media-types in a single definition? I've tried using a vec in the definition, but that doesn't work. I've considered just implementing duplicate endpoints with different media-types, but the ranking system complicates matters. Am I correct in my observation that the format does not play in to the rank at all? That seems like an oversight. I should be able to have two identical endpoints that differ only by format and Rocket should be able to route based on the Accept header.
Unfortunately, there's no way to dynamically add a media type to the list of known media types. The challenge is that warnings are emitted at compile-time whereas configuration can be completely interpreted at runtime. That is, using Rocket.toml is the default configuration source, but it can be completely replaced by anything at all, including over the network, a different file, etc. So reading something like Rocket.toml at compile-time will work but changes the meaning of configuration.
One idea I've had is to add a rocket::allow codegen attribute that can be used on routes to silence warnings:
#[rocket::allow(unknown_media_type)]\n#[get(\"/.well-known/webfinger?<resource>\", format = \"application/jrd+json\", rank = 1)]Since the get attribute can read rocket::allow, it can use it to silence warnings that it would otherwise be emitted.
Alternatively, we could add some special syntax that says \"hey, I know this isn't recognized, but I'm okay with it.\" Maybe even abuse raw strings to do so:
\n#[get(\"/.well-known/webfinger?<resource>\", format = r\"application/jrd+json\", rank = 1)]That would work, but might semantically be too weird.
\nIn any case, I'm open to a solution/implementation of either. The former I would accept directly, the latter would require a bit more thought.
\n\n\nAlso, is there a way to use multiple media-types in a single definition?
\n
No, but I don't see why we couldn't allow multiple formats! I'd accept a PR implementing this.
\n\nAm I correct in my observation that the format does not play in to the rank at all? That seems like an oversight. I should be able to have two identical endpoints that differ only by format and Rocket should be able to route based on the Accept header.
\n
That's right. It's not clear why Rocket should prefer a route that matches json more or less than one that matches msgpack, which would be what ranking would do. We might want to say that a route that has a format should be preferred over one that doesn't, however. That might make sense. But note that Rocket does route based on the accept header, and it does this via matching, not ranking. What ranking does is tell Rocket which routes to try to match first. That is, which route to prefer. A route matching or not has nothing to do with its rank.
For example, we can have:
\n#[get(\"/\", format = \"msgpack\")]\nfn msgpack() {}\n\n#[get(\"/\", format = \"json\", rank = 2)]\nfn json() {}A request with Accept: application/* would be routed to msgpack and not json, even though they both match, because msgpack is ranked higher than json. A request with Accept: application/json would only be routed to json (it doesn't match msgpack) and a request with Accept: application/msgpack would only be routed to msgpack (it doesn't match json).
Handling "not a known media type" #2503
-
|
What is the right way of handling mandatory media types that are unknown to Rocket? I'm building an ActivityPub service and it uses a lot of media types that aren't defined as "known" by default: #[get(
"/.well-known/webfinger?<resource>",
format = "application/jrd+json",
rank = 1
)]#[post(
"/api/user/<username>/events/authorize",
format = "application/activity+json",
data = "<authorization>"
)]#[get("/.well-known/host-meta", format = "application/xrd+xml")]And so forth. These are all well-known types (except for maybe Also, is there a way to use multiple media-types in a single definition? I've tried using a vec in the definition, but that doesn't work. I've considered just implementing duplicate endpoints with different media-types, but the ranking system complicates matters. Am I correct in my observation that the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Unfortunately, there's no way to dynamically add a media type to the list of known media types. The challenge is that warnings are emitted at compile-time whereas configuration can be completely interpreted at runtime. That is, using One idea I've had is to add a #[rocket::allow(unknown_media_type)]
#[get("/.well-known/webfinger?<resource>", format = "application/jrd+json", rank = 1)]Since the Alternatively, we could add some special syntax that says "hey, I know this isn't recognized, but I'm okay with it." Maybe even abuse raw strings to do so: #[get("/.well-known/webfinger?<resource>", format = r"application/jrd+json", rank = 1)]That would work, but might semantically be too weird. In any case, I'm open to a solution/implementation of either. The former I would accept directly, the latter would require a bit more thought.
No, but I don't see why we couldn't allow multiple
That's right. It's not clear why Rocket should prefer a route that matches For example, we can have: #[get("/", format = "msgpack")]
fn msgpack() {}
#[get("/", format = "json", rank = 2)]
fn json() {}A request with |
Beta Was this translation helpful? Give feedback.
-
|
Coming back to this very late, but thank you for the thorough explanation. The differentiation between I confess that macros seem a bit like black magic to me at the moment, but I do have a book on writing Rust macros on my desk that I plan on reading soon. I'll see if I can write something around the "rocket::allow" suggestion you've made above (if it hasn't been done already). |
Beta Was this translation helpful? Give feedback.
-
|
@justindthomas Rocket now has a way to suppress warnings: https://api.rocket.rs/master/rocket/attr.suppress |
Beta Was this translation helpful? Give feedback.
-
|
Nice, thanks. Will that be merged to the 0.5 branch? I tried moving to 0.6.0-dev, but it looks like the changes required to my code base are substantial. |
Beta Was this translation helpful? Give feedback.
Unfortunately, there's no way to dynamically add a media type to the list of known media types. The challenge is that warnings are emitted at compile-time whereas configuration can be completely interpreted at runtime. That is, using
Rocket.tomlis the default configuration source, but it can be completely replaced by anything at all, including over the network, a different file, etc. So reading something like Rocket.toml at compile-time will work but changes the meaning of configuration.One idea I've had is to add a
rocket::allowcodegen attribute that can be used on routes to silence warnings: