Opened 18 months ago

Last modified 18 months 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

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://stackoverflow.com/questions/31939971/serving-static-files-with-content-negotiation-using-embedded-jetty
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.

Subtickets

Change History (1)

Note: See TracTickets for help on using tickets.