rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: "Marc-André Cournoyer" <macournoyer@gmail.com>
To: Hongli Lai <honglilai@gmail.com>
Cc: Eric Wong <e@80x24.org>, rack-devel@googlegroups.com
Subject: Re: Close body object after socket hijacking or not?
Date: Thu, 4 Jun 2015 08:38:42 -0400	[thread overview]
Message-ID: <CACkZu0rzACsz753yQnf4oEmtsBB=3ZRssOMUFUXtBj09ezCd=g@mail.gmail.com> (raw)
In-Reply-To: <CAM3ce8G2FUY-y_EhKOZs7vqYjs-ag7pfwWjjSsdepyFop-m=Tg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]

Indeed, no support for hijacking planned in Thin atm.

On Thu, Jun 4, 2015 at 2:53 AM, Hongli Lai <honglilai@gmail.com> wrote:

> On Thu, Jun 4, 2015 at 4:11 AM, Eric Wong <e@80x24.org> wrote:
> > Where does thin do this?  I can see puma doing it, but it doesn't look
> > like thin supports hijack at all.
> >
> > git clone git://github.com/macournoyer/thin && cd thin && git grep -i
> hijack
> > <no output from git grep>
>
> You are right. It seems I am mistaken about this and got confused with
> another related aspect I was researching.
>
> I was researching
> https://github.com/ngauthier/tubesock/issues/10#issuecomment-72539461
> and came to the conclusion that the bug doesn't occur in the same way
> on Thin, and somehow I got confused later on to conclude that Thin
> supports hijacking.
>



-- 
M-A
http://macournoyer.com

-- 

--- 
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.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 2044 bytes --]

  reply	other threads:[~2015-06-04 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 21:26 Close body object after socket hijacking or not? Hongli Lai
2015-04-17 20:43 ` Eric Wong
2015-05-29 14:09   ` Hongli Lai
2015-06-04  2:11     ` Eric Wong
2015-06-04  6:53       ` Hongli Lai
2015-06-04 12:38         ` Marc-André Cournoyer [this message]
2015-06-28 20:46           ` 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='CACkZu0rzACsz753yQnf4oEmtsBB=3ZRssOMUFUXtBj09ezCd=g@mail.gmail.com' \
    --to=rack-devel@googlegroups.com \
    --cc=e@80x24.org \
    --cc=honglilai@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).