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.

Sign up for GitHub

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

Jump to bottom

Throw warning if ServletInputStream.transferTo(OutputStream) is used while in Async ReadListener is in use? #11663

Open
joakime opened this issue Apr 18, 2024 · 1 comment
Open

Throw warning if ServletInputStream.transferTo(OutputStream) is used while in Async ReadListener is in use? #11663

joakime opened this issue Apr 18, 2024 · 1 comment
Labels
Enhancement Specification For all industry Specifications (IETF / Servlet / etc)

Comments

@joakime
Copy link
Contributor

joakime commented Apr 18, 2024

Jetty version(s)
12.0.8

Enhancement Description

If a Servlet is in an active ReadListener mode (Async Read), and there is code that attempts to use ServletInputStream.transferTo() style methods (that result in multiple read attempts) then it I think using that method should throw an IllegalStateException indicating that this method is unsupported during ReadListener operations.
@joakime
Copy link
Contributor Author

joakime commented Apr 18, 2024

This is a topic opened up at the Servlet spec at jakartaee/servlet#301

@joakime joakime added the Specification For all industry Specifications (IETF / Servlet / etc) label Apr 18, 2024
@joakime joakime changed the title Throw warning if ServletInputStream.transferTo(ByteBuffer) is used while in Async ReadListener is in use? Throw warning if ServletInputStream.transferTo(OutputStream) is used while in Async ReadListener is in use? Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement Specification For all industry Specifications (IETF / Servlet / etc)
Projects
Jetty 12.0.10
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joakime