-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Packetbeat] HTTP: Improve support for 100-continue #15830 #19349
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
💚 CLA has been signed |
Pinging @elastic/siem (Team:SIEM) |
jenkins run tests |
@marc-gr |
It seems to be OK now, maybe the email used to commit was different than the one you used to sign before. Thanks! |
jenkins run tests |
jenkins run tests |
It seems it has linting issues:
You can fix this by running Thanks! |
@marc-gr To Be Reviewed |
jenkins run tests |
jenkins run tests |
@OhBonsai I merged master since tests were red and your branch was quite behind |
@marc-gr Thanks... So there is anything else I need to do ? |
Co-authored-by: Adrian Serrano <[email protected]>
jenkins, test this |
jenkins run tests |
…astic#19349) * refactor(packet beat): Improve support for 100-continue * test(packetbeat): 100-continue only generate one event without error * test(packetbeat): 100-continue only generate one event without error * Update packetbeat/protos/http/http.go Co-authored-by: Adrian Serrano <[email protected]> * delete unused string * Fix format issue Co-authored-by: Marc Guasch <[email protected]> Co-authored-by: Adrian Serrano <[email protected]> (cherry picked from commit 41bc8c6)
…ne-2.0 * upstream/master: (41 commits) adding possibility to override content-type checks, it was breaking certain webhooks that is not able to set content-headers at all. Still defaults to application/json (elastic#20232) fix: use a fixed worker type for tests (elastic#20130) [Ingest Manager] Prepare packaging for endpoint and asc files (elastic#20186) [Packetbeat] HTTP: Improve support for 100-continue elastic#15830 (elastic#19349) Increase index.max_docvalue_fields_search to 200 (elastic#20218) [Ingest Manager] Prevent closing closed reader (elastic#20214) [Metricbeat] Use MySQL Host Parser in Query metricset (elastic#20191) Testing: Ignore timestamp from cylance/protect dataset (elastic#20211) [Filebeat] Ignore cylance.protect timestamps while testing (elastic#20207) [CI] remove codecov step (elastic#20102) [docs] Indicate that SYSTEM user is required on Windows to use Endpoint (elastic#20172) Remove f5/firepass rsa2elk fileset (elastic#20160) [Elastic Agent] Improve GRPC stop to be more relaxed. (elastic#20118) Fix fileset field prefixing (elastic#20170) Fix terminating pod autodiscover issue (elastic#20084) Call host parser only once when building light metricsets (elastic#20149) [CI] fix null string with contains (elastic#20182) [Ingest Manager] Fix failing unit tests on windows (elastic#20127) [Filebeat] Update crowdstrike module (elastic#20138) [docs] Add x-pack role to relevant metricsets (elastic#20167) ...
…20234) * refactor(packet beat): Improve support for 100-continue * test(packetbeat): 100-continue only generate one event without error * test(packetbeat): 100-continue only generate one event without error * Update packetbeat/protos/http/http.go Co-authored-by: Adrian Serrano <[email protected]> * delete unused string * Fix format issue Co-authored-by: Marc Guasch <[email protected]> Co-authored-by: Adrian Serrano <[email protected]> (cherry picked from commit 41bc8c6) Co-authored-by: Bonsai <[email protected]>
…astic#19349) * refactor(packet beat): Improve support for 100-continue * test(packetbeat): 100-continue only generate one event without error * test(packetbeat): 100-continue only generate one event without error * Update packetbeat/protos/http/http.go Co-authored-by: Adrian Serrano <[email protected]> * delete unused string * Fix format issue Co-authored-by: Marc Guasch <[email protected]> Co-authored-by: Adrian Serrano <[email protected]>
What does this PR do?
Improve support for 100-continue #15830
Checklist
How to test this PR locally
nosetests ./tests/system/test_0070_http_100_continue.py
Related issues
#15830