Add support for content negotiation to I2PDefaultservlet
Opened 3 years ago
Last modified 3 years ago
#2269newenhancement
Add support for content negotiation to I2PDefaultservlet
Reported by:zzzOwned by: Priority: minor Milestone: 0.9.37 Component: apps/jetty Version: 0.9.34 Keywords:
Cc:
Parent Tickets:
Sensitive: no
Description
For static content. This will allow the eepsite help page for the correct language to load locally. Could also be useful for production eepsites. Need to define the naming scheme; is foo_xx.ext ok? Must we support foo_xx_YY.ext? Any standard practices?
Is there Jetty code to parse the Accept-Language header including fallbacks?
ref:
https://httpd.apache.org/docs/current/content-negotiation.html
https://tools.ietf.org/html/rfc7231#section-5.3.5
https://tools.ietf.org/html/rfc4647#section-2.3 et seq.