Skip to content

Ensure original URLs are redirected (301 Moved Permanently) to normalized names, including pages that has redirects #6

@renoirb

Description

@renoirb

Once we have #3 addressed, we’ll have to configure web server to make proper HTTP redirection for funny URL names and others that may create conflicts (e.g. inconsistent casing #2)

Handle cases such as:

  • tutorials/What is CSS? into tutorials/What_is_CSS
  • concepts/accessibility/definitions/visual impairment into concepts/accessibility/definitions/visual_impairment
  • html/elements/!DOCTYPE into html/elements/DOCTYPE
  • svg/properties/animVal (SVGAnimatedString) into svg/properties/animVal_SVGAnimatedString
  • css/Properties/color into css/properties/color (notice "Properties" casing here)
  • css/properties/flex-align into css/properties/align-items (notice casing here too)

Objectives

  1. Keep original URLs in place
  2. Redirect to a valid URL that removes potential confusion (ref: URL "code-points", and RFC3986 at 3.3. Path)
  3. Make obvious mapping from URL into a file name in the source repository

Expected deliverables

Reference

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions