Skip to content

Re-merge "Allow projects with non-ascii asset filenames to be remixed" - #4570

Merged
joshlory merged 2 commits into
stagingfrom
re-merge-non-ascii-remix
Oct 14, 2015
Merged

Re-merge "Allow projects with non-ascii asset filenames to be remixed"#4570
joshlory merged 2 commits into
stagingfrom
re-merge-non-ascii-remix

Conversation

@joshlory

Copy link
Copy Markdown
Contributor

Reverts #4516, re-merging #4481 with a fix for the failing test: a6518b8.

No idea why this only failed in the RACK_ENV=test environment and nowhere else.

@davidsbailey

Copy link
Copy Markdown
Member

Weird. we should probably be URI encoding s3_path too.

@davidsbailey

Copy link
Copy Markdown
Member

LGTM. It looks like of tricky to URL-escape s3_path since it's used in a few places including some where we don't really need to escape it, and apparently this is only giving us problems when copying assets anyway.

joshlory pushed a commit that referenced this pull request Oct 14, 2015
Re-merge "Allow projects with non-ascii asset filenames to be remixed"
@joshlory
joshlory merged commit 6aa9bf7 into staging Oct 14, 2015
@joshlory
joshlory deleted the re-merge-non-ascii-remix branch October 14, 2015 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants