Skip to content

redirect? #12

Description

@bumblefudge

An idea i've been kicking around is that instead of uploading TWO docs at each rotation (/{hash}/did.json AND overwriting /did.json) maybe did.json could just be a symlink or nginx/apache redirect to the current /{hash/ subdirectory? Would that work or do redirects open some can of worms I wasn't thinking about? It would also solve the problem of always being provided the hash of the current signed did doc (because you could extract it from the URL you were redirected to), when used in "legacy mode"

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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