-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Routing for index.html fails with 404 for directories #39871
Comments
I don't consider this a bug, but a feature request and would actually like to know if any other framework behaves as is asked for here. |
@geoand why so? Since it behaves that way in JVM mode shouldn't we consider it a bug if it behaves differently in native? I also think the |
Ah sorry, I misread the part where it worked in JVM mode - my bad. |
I'll check it out |
I had something I thought would fix the issue but it doesn't... Given that there is no logging in |
Sounds like you will need to compile with |
Thanks! But in the meantime I realized the error of my ways :). #39878 is the fix but I still need to add a test |
Ensure that index.html works in any directory in native mode
Describe the bug
I have static html inside src/main/resources/META-INF/resources, if I a put a directory inside that path with an index.html it fails with 404 when I make a GET /{directory}
In local and jvm mode it does return the html
Repo: https://github.com/yazalulloa/routing-assets-example
Expected behavior
When a request is done to a path (GET /users) that has a folder with an index.html return the html
Actual behavior
GET /users returns 404
How to Reproduce?
There is a Dockerfile and a bash script to generate the native image and run the container
Make a GET request to /users
Output of
uname -a
orver
No response
Output of
java -version
Java 21
Mandrel or GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.9.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.6
Additional information
No response
The text was updated successfully, but these errors were encountered: