[Bug 69735] New: Support content negotiation for Accept-Language (static pages)

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69735

Bug ID: 69735
   Summary: Support content negotiation for Accept-Language
(static pages)
   Product: Tomcat 11
   Version: unspecified
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Connectors
  Assignee: dev@tomcat.apache.org
  Reporter: fabstz...@yahoo.fr
  Target Milestone: ---

Add support for content negotiation like apache httpd [1] does for the
Accept-Language header.

Use case is serving static pages with "href=my_page.html" and where files in
the webapp folder are actually

my_page.html.en
my_page.html.de
my_page.html.fr
my_page.html.it
...

At the moment, when trying to load my_page.html it shows 404 error.

The idea here is to serve static pages that don't go through a servlet.

The table at [2] might be of interest: 

[1] https://httpd.apache.org/docs/current/content-negotiation.html
[2] https://httpd.apache.org/docs/current/en/content-negotiation.html#naming

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 69735] Support content negotiation for Accept-Language (static pages)

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69735

--- Comment #1 from fabstz...@yahoo.fr ---
See also: https://lists.apache.org/thread/2l559qcqdl5qhwgc7p0sdxww2v9b1pk5

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 69735] Support content negotiation for Accept-Language (static pages)

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69735

fabstz...@yahoo.fr changed:

   What|Removed |Added

   Severity|normal  |enhancement

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[Bug 69735] Support content negotiation for Accept-Language (static pages)

2025-07-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69735

--- Comment #2 from Christopher Schultz  ---
Created attachment 40056
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=40056&action=edit
Initial implementation as a servlet Filter

This is my first effort at a ContentNegotiationFilter which handles the
Accept-Language header only. It's not particularly high-performance, but these
kinds of things are necessarily slower than the straight-ahead path.

I implemented this as a Filter, so it loses several potential benefits of being
implemented inside of Tomcat's DefaultServlet:

1. Tomcat's DefaultServlet will know "better" if the file is found or not. This
Filter uses ServletContext.getResourcePaths() which may not be the best
implementation for discovering if a file exists or not. It also doesn't resolve
anything like whether a Servlet should respond, etc.

2. If the file is not found, or if an exist-match is found -- cases where this
Filter will take no meaningful action -- the DefaultServlet will have to repeat
all of the work to locate the file, etc. If the Filter and the DefaultServlet
could work together (because the code is all in the same place), significant
performance improvements could be had.

3. Since the DefaultServlet knows how to serve files directly, no request
dispatcher.forward() would be necessary if this were implemented in the
DefaultServlet.

There are probably some security concerns about this naïve implementation, but
I wanted to know if I was on the right track for a Filter-based implementation,
or if this is something we would want to build directly into the DefaultServlet
(maybe only eventually, with a Filter being a stop-gap).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: [PR] Filter to limit target file size of ranged put request [tomcat]

2025-07-09 Thread via GitHub


Chenjp closed pull request #873: Filter to limit target file size of ranged put 
request
URL: https://github.com/apache/tomcat/pull/873


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org