On 07/24/2015 02:09 PM, ic...@apache.org wrote:
> Author: icing
> Date: Fri Jul 24 12:09:44 2015
> New Revision: 1692486
>
> URL: http://svn.apache.org/r1692486
> Log:
> new Protocols directive and core API changes to enable protocol switching on
> HTTP Upgrade or ALPN, implemented in mod_ssl
On Wed, Sep 2, 2015 at 4:31 PM, Stefan Eissing
wrote:
>
>> Am 02.09.2015 um 16:19 schrieb Yann Ylavic :
>>
>> On Wed, Sep 2, 2015 at 4:04 PM, Eric Covener wrote:
>>> On Wed, Sep 2, 2015 at 10:01 AM, Stefan Eissing
>>>
But would it have an "Upgrade: + Connection:" header? I might be wrong, but I
thought mod_proxy_wstunnel adds those headers before sending the request to a
backend. So the core_ugprade_handler would not see those.
> Am 02.09.2015 um 16:04 schrieb Eric Covener :
>
> On Wed,
> Am 02.09.2015 um 15:16 schrieb Yann Ylavic :
>
> I wonder how these handlers interact with mod_proxy_wstunnel which
> needs to handle the Upgrade by itself (after the HTTP header has been
> forwarded to the backend).
>
> I'm not sure we can upgrade unconditionally really
On Wed, Sep 2, 2015 at 10:01 AM, Stefan Eissing
wrote:
> Hmm. Is the
> ap_hook_handler(core_upgrade_handler,NULL,NULL,APR_HOOK_REALLY_FIRST);
> called for requests that mod_proxy_wstunnel makes against a backend?
yes, the guts of mod_proxy is just a handler, so
On Fri, Jul 24, 2015 at 2:09 PM, wrote:
> Author: icing
> Date: Fri Jul 24 12:09:44 2015
> New Revision: 1692486
>
> URL: http://svn.apache.org/r1692486
> Log:
> new Protocols directive and core API changes to enable protocol switching on
> HTTP Upgrade or ALPN, implemented in
On Wed, Sep 2, 2015 at 4:04 PM, Eric Covener wrote:
> On Wed, Sep 2, 2015 at 10:01 AM, Stefan Eissing
> wrote:
>> Hmm. Is the
>> ap_hook_handler(core_upgrade_handler,NULL,NULL,APR_HOOK_REALLY_FIRST);
>> called for requests that
> Am 02.09.2015 um 16:12 schrieb Eric Covener :
>
> On Wed, Sep 2, 2015 at 10:09 AM, Stefan Eissing
> wrote:
>> But would it have an "Upgrade: + Connection:" header? I might be wrong, but
>> I thought mod_proxy_wstunnel adds those headers before
On Wed, Sep 2, 2015 at 10:09 AM, Stefan Eissing
wrote:
> But would it have an "Upgrade: + Connection:" header? I might be wrong, but I
> thought mod_proxy_wstunnel adds those headers before sending the request to a
> backend. So the core_ugprade_handler would not
> Am 02.09.2015 um 16:19 schrieb Yann Ylavic :
>
> On Wed, Sep 2, 2015 at 4:04 PM, Eric Covener wrote:
>> On Wed, Sep 2, 2015 at 10:01 AM, Stefan Eissing
>> wrote:
>>> Hmm. Is the
>>>
Done in r1696266.
Am 24.07.2015 um 15:54 schrieb Ruediger Pluem rpl...@apache.org:
+
+/* make sure httpd closes the connection after this */
+c-keepalive = AP_CONN_CLOSE;
+ap_lingering_close(c);
+
+
On 07/24/2015 03:50 PM, Stefan Eissing wrote:
Am 24.07.2015 um 15:40 schrieb Ruediger Pluem rpl...@apache.org:
On 07/24/2015 02:09 PM, ic...@apache.org wrote:
Author: icing
Date: Fri Jul 24 12:09:44 2015
New Revision: 1692486
+static int core_upgrade_handler(request_rec *r)
+{
+
Am 24.07.2015 um 15:54 schrieb Ruediger Pluem rpl...@apache.org:
The c-keepalive = AP_CONN_CLOSE looks fine to me, but why should we do the
other stuff in a handler.
IMHO that should be done by the existing code.
Not sure I understand. You mean the interim response or the whole handler?
On 07/24/2015 02:09 PM, ic...@apache.org wrote:
Author: icing
Date: Fri Jul 24 12:09:44 2015
New Revision: 1692486
URL: http://svn.apache.org/r1692486
Log:
new Protocols directive and core API changes to enable protocol switching on
HTTP Upgrade or ALPN, implemented in mod_ssl and
Am 24.07.2015 um 15:40 schrieb Ruediger Pluem rpl...@apache.org:
On 07/24/2015 02:09 PM, ic...@apache.org wrote:
Author: icing
Date: Fri Jul 24 12:09:44 2015
New Revision: 1692486
+
static const char *set_http_protocol(cmd_parms *cmd, void *dummy,
15 matches
Mail list logo