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: disable chunked transfer-encoding
Date: Thu, 23 May 2019 08:19:47 -0700 (PDT)	[thread overview]
Message-ID: <ab1058ab-ba08-4843-9489-86bcc55bde19@googlegroups.com> (raw)


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

Hi,

I'm trying to use Rack as a FastCGI authorizer (cf 
https://github.com/fast-cgi/spec/blob/master/spec.md#63-authorizer ) in 
conjunction with Apache mod_authnz_fcgi 
(https://httpd.apache.org/docs/2.4/mod/mod_authnz_fcgi.html ). My problem 
is that mod_authnz_fcgi insists on a 200 status code and *only* a 200 
status code to communicate any results from the fastcgi script back up the 
line. This is where Rack::Chunked is ruining my day: it forces the choice 
of either a Content-Length header (which is transmitted upstream and 
truncates the output), or a Transfer-Encoding: chunked header where the 
accompanying *token* is removed upstream, resulting in a protocol error.

I would like to be able to express an HTTP 200 response that has neither a 
Content-Length nor a Transfer-Encoding header. Is there any way to disable 
Rack::Chunked for certain responses?

-- 

--- 
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/ab1058ab-ba08-4843-9489-86bcc55bde19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 15:19 dorian taylor [this message]
2019-05-23 16:14 ` disable chunked transfer-encoding 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

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=ab1058ab-ba08-4843-9489-86bcc55bde19@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).