[Bugfix] Handle content type with optional parameters#13383
[Bugfix] Handle content type with optional parameters#13383DarkLight1337 merged 3 commits intovllm-project:mainfrom
Conversation
|
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
e.g. application/json; charset=UTF-8 Signed-off-by: Zifei Tong <zifeitong@gmail.com>
zifeitong
force-pushed
the
fix_content_type_check
branch
from
45b787d to
6556233
Compare
Signed-off-by: Zifei Tong <zifeitong@gmail.com>
Signed-off-by: Zifei Tong <zifeitong@gmail.com>
|
Thanks for fixing! |
github-actions
bot
added
the
ready
…3383) Signed-off-by: Zifei Tong <zifeitong@gmail.com>
…3383) Signed-off-by: Zifei Tong <zifeitong@gmail.com>
…3383) Signed-off-by: Zifei Tong <zifeitong@gmail.com> Signed-off-by: Louis Ulmer <ulmerlouis@gmail.com>
…3383) Signed-off-by: Zifei Tong <zifeitong@gmail.com>
3 participants
Content type is allowed to have multiple optional parameters, e.g.
application/json; charset=UTF-8. It's not correctly handled right now.Follow-up of #13193.