rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: dorian taylor <dorian.taylor@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: disable chunked transfer-encoding
Date: Thu, 23 May 2019 09:54:11 -0700 (PDT)	[thread overview]
Message-ID: <fb1df7ca-7c07-4425-8336-099301549e59@googlegroups.com> (raw)
In-Reply-To: <CABGa_T_d1Z6FaJhewsbP2P6rbtKdAXE_nZFEUfStBYT4DQib4Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]



On Thursday, May 23, 2019 at 9:42:06 AM UTC-7, raggi wrote:

rackup is an opinionated tool that is good for 90% of use cases and adds 
> those middleware to meet that goal.
>
> I would say the behavior you need falls out of that use case set, and you 
> should consider writing your fastcgi spawner using the library primitives.
>
>
Ah, yes, thanks. It'll probably end up that way; I'm just sketching it out 
right now: https://github.com/doriantaylor/rb-lazyauth

Also the 'none' environment indeed seems to skip the stock middleware. 
Thanks!

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rack-devel/fb1df7ca-7c07-4425-8336-099301549e59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1645 bytes --]

      parent reply	other threads:[~2019-05-23 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 15:19 disable chunked transfer-encoding dorian taylor
2019-05-23 16:14 ` dorian taylor
2019-05-23 16:15 ` James Tucker
2019-05-23 16:18   ` dorian taylor
2019-05-23 16:41     ` James Tucker
2019-05-23 16:44       ` James Tucker
2019-05-23 16:54       ` dorian taylor [this message]

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=fb1df7ca-7c07-4425-8336-099301549e59@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).