jetty/jetty.project

Content negotiation for Accept-Language (static pages) ?

Open

#13330 opened on Jul 7, 2025

View on GitHub
 (10 comments) (0 reactions) (1 assignee)Java (3,701 stars) (1,913 forks)batch import
EnhancementHelp Wanted

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

Tech stack
java
Domain
backend
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaHTTP content negotiationJetty static file serving
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Implement content negotiation for Accept Language in Jetty's static file serving module. Refer to Apache httpd's content negotiation documentation. Examine Jetty's ResourceHandler class (in jetty server) to understand how static files are served. Consider adding support for language variants like index.html.en, index.html.de, and implementing a fallback mechanism to default language when no match.