Opened 3 years ago

Last modified 3 years ago

#2269 new enhancement

Add support for content negotiation to I2PDefaultservlet

Reported by: zzz Owned by:
Priority: minor Milestone: 0.9.37
Component: apps/jetty Version: 0.9.34
Keywords: Cc:
Parent Tickets: Sensitive: no


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: et seq.


Change History (1)

Note: See TracTickets for help on using tickets.