From: Jerry West <jerry.west@ntlworld.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: should Rack::Response delete Content-Length on status 204?
Date: Mon, 8 Nov 2010 15:07:25 -0800 (PST) [thread overview]
Message-ID: <03b5568e-26f0-4573-bd1f-31e0d44b0e6d@i32g2000pri.googlegroups.com> (raw)
In-Reply-To: <eb4f5ce9-7ed9-4206-b4ae-2e43acf84953@v20g2000prl.googlegroups.com>
No I won't - there are no issues on your fork so I've left it on
chneukirchen.
And I really shouldn't post before thinking it through...
Cheers.
On Nov 8, 11:00 pm, Jerry West <jerry.w...@ntlworld.com> wrote:
> Sorry, noob here - do you mean chneukirchen/rack or your fork?
>
> On second thoughts, I'll do both, apologies for the duplication.
>
next prev parent reply other threads:[~2010-11-08 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 22:40 should Rack::Response delete Content-Length on status 204? Jerry West
2010-11-07 22:09 ` James Tucker
2010-11-08 23:00 ` Jerry West
2010-11-08 23:07 ` Jerry West [this message]
2010-11-11 6:51 ` James Tucker
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03b5568e-26f0-4573-bd1f-31e0d44b0e6d@i32g2000pri.googlegroups.com \
--to=rack-devel@googlegroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).