Repository navigation
[JENKINS-39034] /i18n/resourceBundle should be conform to the w3c standard about locale negotiation #17610
Description
https://www.w3.org/International/questions/qa-lang-priorities talks about the negotiation between browser and server:
The basic rule here is that if your language preference list contains a language tag containing a hyphen, such as fr-CH (French as spoken in Switzerland), you should consider adding an additional language tag without the hyphen, ie. fr (French) in this case, immediately after.
This is because if a server follows the HTTP/1.1 specification literally, it is unable to match fr-CH against a document labelled on the server as fr.
In our case the server side is awaiting for a second (separate) parameter country however to allow direct interaction we should allow to detect region/country locale preferences from the language parameter.
Originally reported by 
tscherler, imported from: /i18n/resourceBundle should be conform to the w3c standard about locale negotiation
- assignee:
tfennelly
- status: Closed
- priority: Minor
- component(s): blueocean-plugin, core
- resolution: Duplicate
- resolved: 2016-11-24T07:46:19+00:00
- votes: 0
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
https://www.w3.org/International/questions/qa-lang-priorities talks about the negotiation between browser and server:
The basic rule here is that if your language preference list contains a language tag containing a hyphen, such as fr-CH (French as spoken in Switzerland), you should consider adding an additional language tag without the hyphen, ie. fr (French) in this case, immediately after.
This is because if a server follows the HTTP/1.1 specification literally, it is unable to match fr-CH against a document labelled on the server as fr.
In our case the server side is awaiting for a second (separate) parameter country however to allow direct interaction we should allow to detect region/country locale preferences from the language parameter.
Activity
jenkins-infra-bot commentedon Nov 24, 2016
Raw content of original comment:
Adding the component blueocean-plugin so this shows up on our agile board.
jenkins-infra-bot commentedon Nov 24, 2016
Raw content of original comment:
Already covered by
JENKINS-39891jenkins-infra-bot commentedon Nov 24, 2016
Raw content of original comment:
jamesdumay that ticket had been only for jenkins core. blueocean has nothing to do with it.
jenkins-infra-bot commentedon Nov 24, 2016
Raw content of original comment:
tscherler sure but our team wrote it. We should be good citizens!
jenkins-infra-bot commentedon Nov 24, 2016
Raw content of original comment:
not sure if I understand. The code only is for core. If we want it in BO then we should not reuse an "old" ticket which is already closed, that is my point.
More because the test cases in core point to this ticket.
jenkins-infra-bot commentedon Nov 24, 2025
[Original
is_duplicated_byfrom Jira: JENKINS-39891]