Skip to content

API reference "latest" pages should yield HTTP status 301 not 404 #1435

Description

@chalin

Visit one of the API reference pages and you'll initially get a 404, for example opentelemetry-sdk/latest:

$ curl -I https://open-telemetry.github.io/opentelemetry-ruby/opentelemetry-sdk/latest
HTTP/2 404 

If you open the same link in a browser, then the page redirects because it contains JS code that manipulates the window location to refer to the latest version of the appropriate Gem.

Since API reference pages get redirected the proper HTTP status returned should be 301, not 404. Otherwise, that's bad for SEO and for link checkers -- e.g., see https://github.com/open-telemetry/opentelemetry.io/pull/2505/files#r1135889989.

/cc @cartermp @svrnm

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions