jetty/jetty.project

Content negotiation for Accept-Language (static pages) ?

Closed

#13,330 opened on Jul 7, 2025

View on GitHubContributor guide
 (10 comments) (0 reactions) (1 assignee)Java (1,913 forks)batch import
EnhancementHelp Wanted

Repository metrics

Stars
 (3,701 stars)
PR merge metrics
 (Avg merge 6d 14h) (48 merged PRs in 30d)

Description

I'm creating this issue as suggested on the list .

Request: Add support for content negotiation like apache httpd 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.

Contributor guide

Research direction
Investigate Jetty's current content negotiation mechanism (e.g., for Accept Encoding) and extend it to support Accept Language for static resources. Look at how Apache httpd implements language negotiation (MultiViews) and design a similar approach using file extensions (.en, .de, etc.). Examine the ResourceHandler and DefaultServlet classes to understand where to intercept requests and select the appropriate variant based on the Accept Language header.
Tech stack
java
Domain
backendweb dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaHTTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45