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

Clarify implicit mappings and welcome file behaviour #20

Open
glassfishrobot opened this issue Oct 7, 2011 · 4 comments
Open

Clarify implicit mappings and welcome file behaviour #20

glassfishrobot opened this issue Oct 7, 2011 · 4 comments
Assignees
Labels
Candidate4NextRelease This issues should be consider for inclusion in the next release project. Enhancement New feature or request

Comments

@glassfishrobot
Copy link

Consider the following:
*.do is mapped to a servlet
welcome files are index.jsp, index.do

The intention is that the index.jsp page should be used if present and index.do (which always maps to the servlet) used if it is not. However, a strict reading of the servlet spec requires that a 404 is returned in index.jsp is not present .

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by markt_asf

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
gregwilkins said:
The problem with this mechanism is that it was designed (and named) for welcome files. This has been somewhat subverted to allow for welcome servlets - ie if *.jsp is mapped to a servlet, then you get this 404 issue.

I believe the solution is to have a separate welcome servlet configuration, that would allow index.do to be attempted even though there is not a index.do file that exists.

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA SERVLET_SPEC-20

@glassfishrobot
Copy link
Author

@glassfishrobot glassfishrobot self-assigned this Jun 6, 2018
@gregw gregw added Enhancement New feature or request and removed Component: Misc labels Jan 18, 2020
@gregw gregw added the Candidate4NextRelease This issues should be consider for inclusion in the next release project. label Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Candidate4NextRelease This issues should be consider for inclusion in the next release project. Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants