There is a mechanism for you to define additional types. I think you will need to define each version as its own mime type.
josevalim
Creator of Elixir
altdsoy
Hello José, did you mean setting the types in the config :mime, :types (as it’s suppose to be done)?
Maybe, I was a bit confusing, sorry for that. I meant that I was able to define my own type using the following:
config :mime, :types,
"application/vnd.example.v1+json" => ["v1"],
"application/vnd.example.v2+json" => ["v2"]
}
However, It seems that the below version does not work, and it was basically my question (just wanted to be sure it doesn’t work as a MIME type):
config :mime, :types,
"application/vnd.example+json;version=1" => ["v1"],
"application/vnd.example+json;version=2" => ["v2"]
}
The way I tested it was to using a plug :accepts and it’s only working without the ;version=1.
Anyway, thank you for your time.
0
josevalim
Creator of Elixir
altdsoy
Yes, I did. Double checked ervery time. Running after each change: mix deps.clean mime --build
The MIME that is using the semicolon separated version does not work (I mean the plug :accepts, ["v1"] errors kicks in with a 406 response (which is the expected behavior for a not compatible type, right?)
The one without the semicolon works as expected.
0
josevalim
Creator of Elixir
Hrm, so we need to see how the mime types are being parsed by Plug. Perhaps it rejects or discards what is after the question mark.
0