You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
To do this we would route archive.kchungradio.org to a custom service that would lookup the record in our database and then 301 redirect the client to the appropriate url.
On the browser side, it looks like the CSS working group decided that text-transform shouldn't affect copying of text. Firefox preserves the underlying case of the copied text, but Chrome still applies the transform. Hopefully this will be fixed in webkit.
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?
The text was updated successfully, but these errors were encountered: