Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement path validations #1740

Closed
wants to merge 1 commit into from
Closed

Commits on Sep 22, 2015

  1. Implement path validations

    Per my proposal in ipfs#1710:
      - Paths must be valid UTF-8 per RFC 3629.
      - Paths may not contain ASCII/Unicode C0 control characters
        (U+0000-U+001F).
      - Paths may not contain ASCII DEL (U+007F).
      - Paths are delimited by `/` (U+002F), and therefore path segments may not
        contain it.
      - Path segments may contain up to 255 Unicode codepoints. Total path
        length remains unbounded.
      - Path segments may not be empty, so that `foo//bar` can mean `foo/bar`, as
        in POSIX.
      - Path segments must not be `.` and `..`, so that these can mean what they
        do in POSIX.
    
    Paths may contain any sequence of Unicode codepoints that are not otherwise
    prohibited. This includes many things that could prove problematic; see
    path/validation_test.go +121 for some examples.
    
    License: MIT
    willglynn committed Sep 22, 2015
    Configuration menu
    Copy the full SHA
    b8b0870 View commit details
    Browse the repository at this point in the history