-
Notifications
You must be signed in to change notification settings - Fork 84
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
Use Built-in Java HTTP Server instead of Jetty 11 #2315
base: 4.9.x
Are you sure you want to change the base?
Conversation
import java.util.concurrent.atomic.AtomicBoolean; | ||
|
||
@Internal | ||
class HttpServerEmbeddedServer implements EmbeddedServer { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@graemerocher @yawkat I would like to move this class to core. What do you think? That way I could use it in every cloud module (aws, gcp, azure).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or maybe in servlet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to putting it into servlet
bd0afdc
to
9aa83fe
Compare
|
Jetty 11 has a CVE. This pull request removes the usage of Jetty 11 and replaces it with the built-in Java HTTP Server.
Jetty 12 Handler uses
org.eclipse.jetty.server.Request
instead ofjakarta.servlet.http.HttpServletRequest
.org.eclipse.jetty.server.Request
no longer implementsHttpServletRequest
. Because of that, to get rid of Jetty 11, we had two options: rewrite to Jetty 12 or migrateAwsApiProxyTestServer
to use the Java Built-in HTTP Server and remove the usage of Jetty.I gone the path of using the built-in HTTP Server. There are several classes introduced in this PR which I think should be in micronaut core.