Re: [Rails] InvalidURIError - how to clean up URIs before using .open()

[Hassan Schroeder]

On Tue, Jan 18, 2011 at 5:38 PM, CuriousNewbie <bhellm...@gmail.com> wrote:
> Hello, I got the following back from delayed_job:
>
>    [Worker(XXXXXX pid:3720)] Class#XXXXXXX failed with
> URI::InvalidURIError: bad URI(is not URI?):
> https://s3.amazonaws.com/cline-local-dev/2/attachments/542/original/mac-os-x[1].jpeg?AWSAccessKeyId=xxxxxxxx&Expires=1295403309&Signature=xxxxxxx%3D

> That being said, is there some type of URI.encode or parsing I can do
> to prevent a valid URI (as I checked the URL works in my browser) for
erroring...

and, sorry, that *doesn't* mean it's valid.

via: http://www.ietf.org/rfc/rfc1738.txt

<q>
Other characters are unsafe because
   gateways and other transport agents are known to sometimes modify
   such characters. These characters are "{", "}", "|", "\", "^", "~",
   "[", "]", and "`".

   All unsafe characters must always be encoded within a URL.
</q>

HTH,
-- 
Hassan Schroeder ------------------------ hassan.schroe...@gmail.com
twitter: @hassan

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.