Add support for content negotiation to I2PDefaultservlet #343

Open
opened 2025-04-21 15:07:40 -04:00 by idk · 1 comment
Owner

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://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

Opened [3 years ago](/timeline?from=2018-06-23T14%3A30%3A39Z&precision=second "See timeline at Jun 23, 2018 2:30:39 PM") Last modified [3 years ago](/timeline?from=2018-06-23T14%3A37%3A29Z&precision=second "See timeline at Jun 23, 2018 2:37:29 PM") ## [\#2269](/ticket/2269)[new](/query?status=new)[enhancement](/query?status=!closed&type=enhancement) # Add support for content negotiation to I2PDefaultservlet Reported by:[zzz](/query?status=!closed&reporter=zzz)Owned by: Priority: [minor](/query?status=!closed&priority=minor) Milestone: [0.9.37](/milestone/0.9.37 "Completed 3 years ago (Oct 4, 2018 11:00:00 AM)") Component: [apps/jetty](/query?status=!closed&component=apps%2Fjetty) Version: [0.9.34](/query?status=!closed&version=0.9.34) Keywords: Cc: Parent Tickets: Sensitive: [no](/query?status=!closed&sensitive=0) ### 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://stackoverflow.com/questions/31939971/serving-static-files-with-content-negotiation-using-embedded-jetty) [​https://httpd.apache.org/docs/current/content-negotiation.html](https://httpd.apache.org/docs/current/content-negotiation.html) [​https://tools.ietf.org/html/rfc7231#section-5.3.5](https://tools.ietf.org/html/rfc7231#section-5.3.5) [​https://tools.ietf.org/html/rfc4647#section-2.3](https://tools.ietf.org/html/rfc4647#section-2.3) et seq. ### Subtickets
idk added this to the 0.9.37 milestone 2025-04-21 15:07:40 -04:00
idk added the #22690.9.37appsjetty labels 2025-04-21 15:07:40 -04:00
Author
Owner
[comment:1](https://trac.i2p2.de/\#comment:1) Changed [3 years ago](https://trac.i2p2.de//timeline?from=2018-06-23T14%3A37%3A29Z&precision=second "See timeline at Jun 23, 2018 2:37:29 PM") by zzz Type:defect → enhancement Need more than just parsing code. Processing is complex. [​https://dev.eclipse.org/mhonarc/lists/jetty-users/msg06857.html](https://trac.i2p2.de/https://dev.eclipse.org/mhonarc/lists/jetty-users/msg06857.html) [​https://github.com/eclipse/jetty.project/issues/458](https://trac.i2p2.de/https://github.com/eclipse/jetty.project/issues/458) [​https://github.com/eclipse/jetty.project/issues/459](https://trac.i2p2.de/https://github.com/eclipse/jetty.project/issues/459)
Sign in to join this conversation.
No Label #2269 0.9.37 apps jetty
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: I2P_Developers/i2p.i2p#343
No description provided.