From: Randy MacLeod <randy.macleod@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 0/3] Apache / PHP upgrades
Date: Thu, 16 Jan 2014 10:24:27 -0500 [thread overview]
Message-ID: <52D7F9AB.5040108@windriver.com> (raw)
In-Reply-To: <1857113.0unWlYmFcc@peggleto-mobl5.ger.corp.intel.com>
On 14-01-16 10:15 AM, Paul Eggleton wrote:
> Hi Randy,
>
> On Thursday 16 January 2014 09:31:28 Randy MacLeod wrote:
>> You asked me about dropping this patch and I've done a bit of digging.
>>
>> My conclusion is that the patch is not integrated into 2.4.7 and
>> it would be "nice to have" since we've supported it so far.
>> It seems that apache2-2.6.x will include the patch.
>>
>> The intended use is primarily to support SPDY as described here:
>> https://technotes.googlecode.com/git/nextprotoneg.html
>> and I skimmed though this:
>>
>> http://googledevelopers.blogspot.ca/2012/04/add-spdy-support-to-your-apache-> server.html
>>
>>
>> As for generating a new patch, the STATUS file in 2.4.7 says:
>> ...
>> * mod_ssl: Add support for Next Protocol Negotiation.
>> Trunk patch:
>> http://svn.apache.org/viewvc?view=revision&revision=1332643
>> 2.4.x patch:
>> Trunk patch works.
>> +1: ben
>> sf says: Needs r1345599, too.
>> And wrowe's comment about the 2.2 patch is also valid for 2.4:
>> http://svn.apache.org/viewvc?view=revision&revision=1354823
>>
>>
>> Does that help? Do you want someone @WR to work on the patch, the
>> mod_spdy module and testing? A few more comments and links given
>> below.
>>
>> ../Randy
>>
>> ---
>>
>> This patch has:
>> Upstream-Status: Backport
>> and I do see the _reworked_ feature and our patch upstream
>> in the git-svn repo:
>> https://github.com/apache/httpd.git
>> specifically, the re-worked commit here:
>>
>> https://github.com/apache/httpd/commit/afa9bc99edf96a8ff3a81786cc4ef52a9f3cf
>> 310
>>
>> and a commit with identical content to our patch here:
>>
>> https://github.com/apache/httpd/commit/79d4d4d3ce586bf526178ed6d05e1b0dca705
>> 1c4
>>
>> but they are both on the trunk branch (aka 2.5) so
>> they are not include in 2.4.7.
>>
>> The original defect is:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=52210
>>
>> OpenSSL 1.0.1 added support for TLS Next Protocol Negotiation (NPN)
>> [1], a feature which allows client and server to negotiate what
>> protocol should be used over the secure connection. I propose
>> adding hooks into mod_ssl to allow other modules to access
>> this feature.
>
>
> Thanks for looking deeper into this. I'm not quite sure what they mean by
> "Trunk patch works" but I just retrieved the trunk patch and tried to apply it
> but there are conflicts; I also tried a cherry-pick on that git repository but
> that didn't work either.
>
> I suspect that it would be good to have someone else who knows more about this
> feature create and test a new patch, so if you have someone who could do that
> that would be great.
Will do. It may have to wait until after the Chinese Spring festival but
we'll get it on the "to do" list.
../Randy
>
> Cheers,
> Paul
>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
prev parent reply other threads:[~2014-01-16 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 10:38 [meta-webserver][PATCH 0/3] Apache / PHP upgrades Paul Eggleton
2014-01-13 10:38 ` [meta-webserver][PATCH 1/3] apache2: update to 2.4.7 Paul Eggleton
2014-01-13 10:38 ` [meta-webserver][PATCH 2/3] modphp: upgrade to 5.5.8 Paul Eggleton
2014-01-13 10:38 ` [meta-webserver][PATCH 3/3] phpmyadmin: update to 4.1.4 Paul Eggleton
2014-01-16 14:31 ` [meta-webserver][PATCH 0/3] Apache / PHP upgrades Randy MacLeod
2014-01-16 15:15 ` Paul Eggleton
2014-01-16 15:24 ` Randy MacLeod [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-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=52D7F9AB.5040108@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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