Skip to content
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

Improving RFC request/response passive parsing #2192

Merged
merged 2 commits into from
Jul 11, 2022

Conversation

Mzack9999
Copy link
Member

@Mzack9999 Mzack9999 commented Jun 21, 2022

Proposed changes

This PR adds a check in the passive parsing helper function that tries to parse passive request/response with the standard library, before switching to placeholder matching.

Checklist

  • Pull request is created against the dev branch
  • All checks passed (lint, unit/integration/regression tests etc.) with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Notes

In this particular case the parsing still fails due to a bug in proxify related to request body length miscalculation (ref projectdiscovery/proxify#135)

@Mzack9999 Mzack9999 added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jun 21, 2022
@Mzack9999 Mzack9999 self-assigned this Jun 21, 2022
@Mzack9999 Mzack9999 added the Status: Review Needed The issue has a PR attached to it which needs to be reviewed label Jun 21, 2022
@Mzack9999 Mzack9999 requested a review from Ice3man543 June 21, 2022 10:10
Copy link
Member

@Ice3man543 Ice3man543 left a comment

Choose a reason for hiding this comment

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

@Mzack9999 we should add a test case with a HTTP response that contains HTTP 1/1 placeholder in the response body so that we can validate the fix works.

@ehsandeep ehsandeep merged commit 1c332bb into dev Jul 11, 2022
@ehsandeep ehsandeep deleted the issue-2068-http-passive-parse branch July 11, 2022 17:13
@ehsandeep ehsandeep added Status: Completed Nothing further to be done with this issue. Awaiting to be closed. and removed Status: Review Needed The issue has a PR attached to it which needs to be reviewed labels Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
3 participants