Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Weird behaviour saving attachments.
Date: Sun, 25 Nov 2007 12:28:34 +0100	[thread overview]
Message-ID: <1195990103-sup-5438@ausone.local> (raw)
In-Reply-To: <1195925357-sup-8894@south>

Excerpts from William Morgan's message of Sat Nov 24 18:34:28 +0100 2007:
> Excerpts from nicolas.pouillard's message of Sat Nov 24 02:25:57 -0800 2007:
> > Sometimes  when  I  save attachment the file name is not properly
> > unquoted and then save a file with double quotes in the name (e.g.
> > "foo.bar").
> 
> Can you track down the MIME header in the raw message that names the
> attachment? 
> 
> If you save the message to disk with 's' and search the file for
> "filename", you should see it. (Probably a Content-Disposition header.)
> 

It  was  the  name  attribute of the Content-Type header that was not unquoted
like Content-Disposition filename. Here is a patch as attachment.

-- 
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: unquote-content-type-name.patch
Type: application/octet-stream
Size: 494 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071125/287d1205/attachment.obj 


  reply	other threads:[~2007-11-25 11:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 10:25 Nicolas Pouillard
2007-11-24 17:34 ` William Morgan
2007-11-25 11:28   ` Nicolas Pouillard [this message]
2007-11-26 20:11     ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1195990103-sup-5438@ausone.local \
    --to=nicolas.pouillard@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox