-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[Bugfix] Handle content type with optional parameters #13383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bugfix] Handle content type with optional parameters #13383
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 <[email protected]>
45b787d
to
6556233
Compare
Signed-off-by: Zifei Tong <[email protected]>
Signed-off-by: Zifei Tong <[email protected]>
Thanks for fixing! |
…3383) Signed-off-by: Zifei Tong <[email protected]>
…3383) Signed-off-by: Zifei Tong <[email protected]>
…3383) Signed-off-by: Zifei Tong <[email protected]> Signed-off-by: Louis Ulmer <[email protected]>
…3383) Signed-off-by: Zifei Tong <[email protected]>
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.