Skip to content

file not found / access denied - use fuzzy matching, or generate better error messages?Β #1

@publicityreform

Description

@publicityreform

primarily a problem if people are trying to directly access files in S3 using copy-and-pasted links from a site that doesn't maintain case on the link text (kchung's sites, and any copycat tumblr subdomains, currently force lowercase, for example). if case / spelling / punctuation are not exact, raw xml is returned showing "access denied" - could we try returning fuzzy matches (allowing case-insensitive results, for example)? or maybe a custom error result that gives better / more friendly options for troubleshooting?

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