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

HTTP and RestEasy-related content review #36661

Merged
merged 1 commit into from
Oct 25, 2023
Merged

HTTP and RestEasy-related content review #36661

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/src/main/asciidoc/http-reference.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,13 @@ include::_attributes.adoc[]
:topics: http,web,webjars,vertx,servlet,undertow
:extensions: io.quarkus:quarkus-vertx-http

This document explains various HTTP features that you can use in Quarkus.
This document clarifies different HTTP functionalities available in Quarkus.

HTTP is provided using Eclipse Vert.x as the base HTTP layer. Servlet's are supported using a modified version of Undertow that
runs on top of Vert.x, and RESTEasy is used to provide Jakarta REST support. If Undertow is present RESTEasy will run as a
Servlet filter, otherwise it will run directly on top of Vert.x with no Servlet involvement.
Eclipse Vert.x supplies the fundamental HTTP layer.
For Servlet support, Quarkus employs a customized Undertow version that operates on top of Vert.x, while Jakarta REST support is delivered through RESTEasy.

When Undertow is present, RESTEasy functions as a Servlet filter.
In its absence, RESTEasy operates directly on Vert.x without involving Servlets.

== Serving Static Resources

Expand Down
Loading