eclipse-vertx/vert.x

#5648

· snazy opened

on Jul 15, 2025

Vert.x does not permit to proxy HTTP/2 requests without <code>:authority</code> pseudo header correctly

bug

#5553

· NilsRenaud opened

on Apr 16, 2025

HttpClient.send doesn't fail on ReadStream failure

bug

#5550

· NilsRenaud opened

on Apr 11, 2025

Closed context can still schedule timer

bug

#5405

· ben1222 opened

on Nov 22, 2024

await(Future future) should immediately return or raise if the future is complete - significant perf improvement

bug

#5402

· doctorpangloss opened

on Nov 21, 2024

WebSocket client: make it possible to supply a custom eventLoop context

enhancement

#5366

· mkouba opened

on Oct 23, 2024

[Regression] - Connection should not process messages when in closed state

bug

#5340

· kitd opened

on Oct 2, 2024

HandlerRegistration.receive does not account for closed event loops

bug

#5337

· Onkelborg opened

on Oct 1, 2024

Support for Unix Domain DatagramSocket

enhancement

#5218

· Eng-Fouad opened

on Jun 1, 2024

Optimize Http 2 header validation

enhancement

#5072

· franz1981 opened

on Jan 17, 2024

Pipe's completion handler possibly executed by the "wrong thread", leading to race conditions

bug

#5049

· sauthieg opened

on Dec 22, 2023

JsonParser continuing processing after exception causes issues for RxJava 3 Adapters

bug

#4623

· DemonicTutor opened

on Feb 22, 2023

EventBus breaks on bad network connection

bug

#4394

· ruslansennov opened

on Jun 8, 2022

Add methods to NetSocket for buffer handling

enhancement

#4341

· erik777 opened

on Apr 21, 2022

Websockets serving cached/wrong responses and potentially have incorrect headers in websocket

bug

#4299

· agapic opened

on Mar 5, 2022

Race condition when use RecordParser with concatMapCompletable and observeOn

bug

#4297

· ben1222 opened

on Mar 1, 2022

Add support for Unix domain datagram sockets when using native epoll/kqueue transport

enhancement

#4038

· vietj opened

on Jul 27, 2021

Http2ServerResponse#write(ByteBuf, boolean, Handler<AsyncResult<Void>>) should take empty trailers into consideration

bug

#3985

· markdr-fr opened

on Jun 28, 2021

httpclient connectTimeout does not work expected

bug

#3805

· jinwik opened

on Feb 12, 2021

Multiple web client connections created instead of utilizing existing initial connection

bug

#3590

· pantinor opened

on Oct 2, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

4.5.24

Scheduled future executions fail w/ NPEs [Netty]

Vert.x does not permit to proxy HTTP/2 requests without <code>:authority</code> pseudo header correctly

HttpClient.send doesn't fail on ReadStream failure

Issue 5337: Handle closed event loops

Closed context can still schedule timer

await(Future future) should immediately return or raise if the future is complete - significant perf improvement

WebSocket client: make it possible to supply a custom eventLoop context

[Regression] - Connection should not process messages when in closed state

HandlerRegistration.receive does not account for closed event loops

Support for Unix Domain DatagramSocket

Optimize Http 2 header validation

5049 fix pipe race condition

Pipe's completion handler possibly executed by the "wrong thread", leading to race conditions

JsonParser continuing processing after exception causes issues for RxJava 3 Adapters

EventBus breaks on bad network connection

Add methods to NetSocket for buffer handling

Websockets serving cached/wrong responses and potentially have incorrect headers in websocket

Race condition when use RecordParser with concatMapCompletable and observeOn

Introduce support for pcap traffic capturing of network traffic

Adding full details on what are the requirements for the SPI

Add support for Unix domain datagram sockets when using native epoll/kqueue transport

Http2ServerResponse#write(ByteBuf, boolean, Handler<AsyncResult<Void>>) should take empty trailers into consideration

httpclient connectTimeout does not work expected

New parser for length field based protocols

Multiple web client connections created instead of utilizing existing initial connection

4.5.24

List view