When the incoming request has an Accept-Language header set then it should use the same for the backend requests.
This is to ensure that the service responds with the correct strings on wikis which allow different language variants, like zhwiki.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | Amire80 | T118882 Honor Accept-Language header to set language variant | |||
Resolved | None | T113002 Let's discuss LanguageConverter |
Event Timeline
Comment Actions
This task is not ready to be worked on yet since Parsoid doesn't honor the Accept-Language header either. First we need to see what the outcome of T113002 is.
Comment Actions
Assigning per https://phabricator.wikimedia.org/T119022#1916790:
"Amir: Define the desired behavior from the user perspective according to the suggestion to write in your preferred variant"
Comment Actions
I think Mobile Content Service should just follow the same approach that is decided in T122942: RFC: Support language variants in the REST API.