From: Skip Tavakkolian <9nut@9netics.com>
To: csant@csant.info, 9fans@cse.psu.edu
Subject: Re: [9fans] Attached "noname" file
Date: Fri, 6 Oct 2006 00:34:33 -0700 [thread overview]
Message-ID: <025ce93115e8a93c181b1b0ea628b531@9netics.com> (raw)
In-Reply-To: <op.tgznnqt8d84skq@fiore.malebolge>
it's in marshal.
cpu% grep -n Content-Disposition /sys/src/cmd/upas/*/*.c | grep ainline
/sys/src/cmd/upas/marshal/marshal.c:389: Bprint(&out, "Content-Disposition: ainline\n");
/sys/src/cmd/upas/marshal/marshal.c:690: Bprint(out, "Content-Disposition: ainline\n");
> It's the
> Content-Disposition: ainline
> that breaks it, since this is an unknown Content-Disposition. I have
> noticed it already several times, and kept meaning to ask about it. The
> correct value should be
> Content-Disposition: inline
> How come several people do have this error? Is it a bug in acme?
next prev parent reply other threads:[~2006-10-06 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 1:25 Joel Salomon
2006-10-06 7:12 ` csant
2006-10-06 7:34 ` Skip Tavakkolian [this message]
2006-10-06 10:04 ` erik quanstrom
2006-10-06 15:38 ` Russ Cox
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=025ce93115e8a93c181b1b0ea628b531@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
--cc=csant@csant.info \
/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;
as well as URLs for NNTP newsgroup(s).