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

Re-enable HttpChannelEventTest and port to ee9 #12477

Open
wants to merge 1 commit into
base: jetty-12.1.x
Choose a base branch
from

Conversation

janbartel
Copy link
Contributor

Port HttpChannelEventTest to ee9 and re-enable it.

@janbartel janbartel self-assigned this Nov 5, 2024
@janbartel janbartel mentioned this pull request Nov 5, 2024
39 tasks
@janbartel
Copy link
Contributor Author

@gregw and/or @sbordet please see the lines commented with //TODO as the 2 failure tests fail because these listener methods are never called. Is this expected?

@janbartel
Copy link
Contributor Author

@gregw and @sbordet nudge

connector.addBean(new HttpChannel.Listener()
{
@Override
public void onRequestFailure(Request request, Throwable failure)
{
//TODO never called
Copy link
Contributor

Choose a reason for hiding this comment

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

The onRequestFailure and onComplete methods will never be called for a bad request in jetty-12, as that is determined in core and thus we do not know what context the bad request would have gone to.

So this test is invalid and we should update the javadoc of the listener class to say as much

connector.addBean(new HttpChannel.Listener()
{
@Override
public void onResponseFailure(Request request, Throwable failure)
{
//TODO this is never called
Copy link
Contributor

Choose a reason for hiding this comment

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

This could be a bug. I see no reason that a response failure within a context cannot be notified like this.
Further analysis required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👀 In review
Development

Successfully merging this pull request may close these issues.

2 participants