Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

filenames with question marks + expiring s3 url = pain #616

Closed
xxx opened this issue Oct 6, 2011 · 4 comments
Closed

filenames with question marks + expiring s3 url = pain #616

xxx opened this issue Oct 6, 2011 · 4 comments

Comments

@xxx
Copy link

xxx commented Oct 6, 2011

We are seeing an issue where filenames that include question marks cannot be linked to with expiring urls because the question mark in the filename is being treated as the beginning of the url query string.

I'm not sure what the best path for fixing this one is.

@sikachu
Copy link
Contributor

sikachu commented Oct 14, 2011

I can see the potential failure there. Can you provide us with a failing test case. It's going to be a bit tricky though, as we're actually delegating to aws/s3 for expiring url generation.

@xxx
Copy link
Author

xxx commented Oct 15, 2011

Yes, I just sent a pull request - #621

@xxx
Copy link
Author

xxx commented Nov 15, 2011

Is there a preferred method to resolve this? I have some bandwidth to work on it, but I don't want to make a fix that can't be merged in.

xxx pushed a commit to xxx/paperclip that referenced this issue Nov 23, 2011
@sikachu
Copy link
Contributor

sikachu commented Dec 12, 2011

I've fixed this one after switch to aws/sdk. I've test cases to cover this, so I think this should be resolved.

@sikachu sikachu closed this as completed Dec 12, 2011
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants