Skip to content

fix: REST API server crash due to malformed multipart POST request#5074

Merged
renecannao merged 1 commit intosysown:v3.0from
wazir-ahmed:fix-multipart-crash
Aug 19, 2025
Merged

fix: REST API server crash due to malformed multipart POST request#5074
renecannao merged 1 commit intosysown:v3.0from
wazir-ahmed:fix-multipart-crash

Conversation

@wazir-ahmed
Copy link
Member

  • Disable POST preprocessing option in libhttpserver.
  • Validate Context-Type header in request handler for POST /sync

Fixes #5072

@wazir-ahmed wazir-ahmed requested a review from JavierJF August 12, 2025 05:11
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @wazir-ahmed, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical server crash issue caused by malformed multipart POST requests. The fix involves two main changes: disabling the automatic POST preprocessing option within the underlying libhttpserver library and implementing explicit content-type validation for POST requests to the /sync endpoint. These changes enhance the REST API's robustness and prevent unexpected server termination when encountering malformed request payloads.

Highlights

  • API Robustness: Implemented content-type validation for POST requests to the /sync endpoint, ensuring only expected content types (JSON, plain text) are processed and rejecting others with a 415 Unsupported Media Type error.
  • Server Stability: Disabled the libhttpserver's internal POST preprocessing feature to prevent crashes when handling malformed multipart POST requests, addressing the root cause of the server instability.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@wazir-ahmed wazir-ahmed requested a review from renecannao August 12, 2025 05:11
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses a server crash caused by malformed multipart POST requests. The fix involves disabling POST preprocessing in libhttpserver and adding manual Content-Type validation for the /sync endpoint. The changes look good and directly address the issue. I have one suggestion to ensure consistent behavior for error responses.

- Disable POST preprocessing option in `libhttpserver`.
- Validate `Context-Type` header in request handler for `POST /sync`

Fixes sysown#5072

Signed-off-by: Wazir Ahmed <wazir@proxysql.com>
@sonarqubecloud
Copy link

@renecannao renecannao merged commit 0d2e9ef into sysown:v3.0 Aug 19, 2025
5 of 7 checks passed
@noizu noizu added this to the Release 3.0.3 milestone Sep 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Proxysql v2.3.2 crash

3 participants