netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe W Damasio <felipewd@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: ebtables extension 'http'
Date: Mon, 25 Jan 2010 15:45:50 -0200	[thread overview]
Message-ID: <8a87046f1001250945p2e666b32m7c2051e00454f8e4@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1001251753560.20906@obet.zrqbmnf.qr>

  Hi Mr. Jan

2010/1/25 Jan Engelhardt <jengelh@medozas.de>:
> The issue is that you would need to replay the tcp handshake.
>
> Case 1:
> - do TCP handshake
> - read out Host: header
> - if proxied
>  - good
> - if not,
>  - have to replay TCP handshake to next host (eww :-)

  Would this be so bad? :-)

  I mean, if I could do this, I could reduce the HTTP traffic from
around 400Mbps to around 100Mbps of domains that the proxy actually do
cares.

  And the rest would be forwarded down the bridge.

  Could I do this with repeating the TCP handshake with the next host?
How could I do this?

  Thanks,

Felipe Damasio
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-01-25 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 13:46 ebtables extension 'http' Felipe W Damasio
2010-01-25 13:54 ` Jan Engelhardt
2010-01-25 14:32   ` Felipe W Damasio
2010-01-25 16:35     ` Jan Engelhardt
2010-01-25 16:50       ` Patrick McHardy
2010-01-25 16:55         ` Jan Engelhardt
2010-01-25 16:57           ` Patrick McHardy
2010-01-25 17:45           ` Felipe W Damasio [this message]
2010-01-25 19:02             ` Pascal Hambourg
2010-01-26  6:29               ` Changli Gao

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=8a87046f1001250945p2e666b32m7c2051e00454f8e4@mail.gmail.com \
    --to=felipewd@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    /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).