1546966 - 404 - History and Json - If articles are not translated

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: General, defect)

Description

[davidscandurra]

What did you do?

When an article is not translated the history and JSON links return 404.
The JSON 404 makes it very hard for crawlers to work with.
I think that history links return 404 is okay but not so neatly it should display an error.
The normal pages just use the English text with a warning I feel like you could do the same thing with history.
Few examples:
https://developer.mozilla.org/de/docs/Web/API/DeviceProximityEvent$history
https://developer.mozilla.org/de/docs/Web/API/SVGFETurbulenceElement$json
https://developer.mozilla.org/ru/docs/Mozilla/Firefox/Releases/23$json
https://developer.mozilla.org/de/docs/Web/API/SVGFETurbulenceElement$json

What happened?

a

What should have happened?

v

Is there anything else we should know?

c

Comment 1

[davidscandurra]

Sorry for the a v c thinks I thought I could remove them later.

Comment 2

[Ryan Johnson (:rjohnson)]

Hi davidscandurra,

I understand your point. We are displaying the English version of a document with a warning when it's not available for a specific locale, and that we should do something similar for the $history and $json endpoints. However, we feel that adding the $history and $json endpoints (and there are others, like $edit) would only increase the appearance that the document exists in that locale, when it doesn't, and might be even more confusing. Our current behavior is perhaps not fully consistent, but we're going to stay with it for now. Thanks though, for your suggestion.