Feature #12038

Please add documentation to open-uri showing how to obtain an attachment

Added by shevegen (Robert A. Heiler) over 4 years ago. Updated over 4 years ago.

Third Party's Issue
Target version:


The current documentation for open-uri is at:

I am trying to download:

This gives a text file (fasta file) which has sequence information for a human gene.

With open-uri I get this metadata:

meta (mathew murphy)=
{"date"=>"Sat, 30 Jan 2016 10:37:29 GMT",
"content-disposition"=>"attachment; filename=sequence.fasta",
"ncbi_sid=9DFD1FFC6AC92691_0807SID;; path=/; expires=Mon, 30 Jan 2017 10:37:29 GMT",
{"date"=>["Sat, 30 Jan 2016 10:37:29 GMT"],
"content-disposition"=>["attachment; filename=sequence.fasta"],
["ncbi_sid=9DFD1FFC6AC92691_0807SID;; path=/; expires=Mon, 30 Jan 2017 10:37:29 GMT"],
@status=["200", "OK"]>

I assume that the important part is:

"content-disposition"=>["attachment; filename=sequence.fasta"]

So there is an attachment.

I googled, found some stackoverflow answers; most refer to rails
though but I want a pure ruby solution.

Now here is my request:

  • Could someone show a simple example for the open-uri documentation in how users are able to obtain an attachment, if this fits to open-uri? (If it does not fit to open-uri, then this can be omitted; but if default ruby provides this, perhaps some documentation can be added for that).

Thanks for reading anyway!

Updated by shevegen (Robert A. Heiler) over 4 years ago

al2o3-cr on IRC showed the solution:

File.write('foo.txt', open("").read)

So it was indeed quite simple.

Maybe some documentation could still be added to open-uri even though this is not a part
of open-uri directly?

Perhaps other people may run into similar situations.

At any rate, I think that this can be closed. Thanks.

Updated by naruse (Yui NARUSE) over 4 years ago

  • Status changed from Open to Third Party's Issue

Also available in: Atom PDF