httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 59176] New: HTTP/2 Internal Error when receiving connections from a proxy over HTTP/2
Date Sun, 13 Mar 2016 14:04:53 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=59176

            Bug ID: 59176
           Summary: HTTP/2 Internal Error when receiving connections from
                    a proxy over HTTP/2
           Product: Apache httpd-2
           Version: 2.4.18
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_http2
          Assignee: bugs@httpd.apache.org
          Reporter: Russel.VanTuyl@gmail.com

Created attachment 33666
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=33666&action=edit
Apache Error Log

I'm using nghttpx version x as proxy to connect to an Apache 2.4.18 instance
built from source. The Apache 2.4.18 instance reports the below error when it
receives connections over HTTP/2 from the nghttpx proxy.

[Sun Mar 13 08:37:41.537125 2016] [http2:debug] [pid 24763:tid 139792823330560]
h2_stream.c(206): [client 192.168.56.120:43987] h2_stream(0-1): reset, error=2
[Sun Mar 13 08:37:41.537263 2016] [http2:debug] [pid 24763:tid 139792823330560]
h2_stream.c(321): [client 192.168.56.120:43987] h2_stream(0-1): RST=2 (internal
err) GET http://(null)/
[Sun Mar 13 08:37:41.537415 2016] [http2:debug] [pid 24763:tid 139792823330560]
h2_session.c(456): (70013)Missing parameter for the specified command line
option: [client 192.168.56.120:43987] AH02923: h2_session: stream(0-1): error
handling frame


The Apache 2.4.18 instance is able to handle HTTP/2 connections when accessed
directly, without the use of nghttpx. I also built Apache 2.4.17 from source
using the same static libraries and configure options. Apache 2.4.17 handles
HTTP/2 proxy connections from nghttpx without error. Both instances of Apache
2.4.18 and 2.4.17 are configured the same. The complete debug output from
error_log for the failed HTTP/2 connection is attached in 'error_log'. Below
are the requests as logged by nghttpx

10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_connection_handler.cc:332
[LISTEN:0x7ffd0f638190] Accepted connection. fd=9
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:338
[CLIENT_HANDLER:0x7f4382cea000] This is HTTP/1.1 connection, but may be
upgraded to HTTP/2 later.
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_https_upstream.cc:69
[UPSTREAM:0x7f4382c720b0] HTTP request started
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_https_upstream.cc:248
[UPSTREAM:0x7f4382c720b0] HTTP request headers completed
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_https_upstream.cc:270
[UPSTREAM:0x7f4382c720b0] HTTP request headers
GET / HTTP/1.1
host: 127.0.0.1:3000
pragma: no-cache
cache-control: no-cache
accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/48.0.2564.109 Safari/537.36
accept-encoding: gzip, deflate, sdch
accept-language: en-US,en;q=0.8
x-forwarded-for: 192.168.56.115
x-forwarded-host: 192.168.56.120
x-forwarded-server: www.example.com
connection: Keep-Alive

10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:702
[CLIENT_HANDLER:0x7f4382cea000] Downstream address group_idx: 0
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:711
[CLIENT_HANDLER:0x7f4382cea000] Downstream connection pool is empty. Create new
one
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:718
[CLIENT_HANDLER:0x7f4382cea000] http2_freelist is empty; create new
Http2Session
10/Mar/2016:23:57:44 -0600 PID17624 [INFO]
shrpx_http2_downstream_connection.cc:95 [DCONN:0x7f4382c633c0] Attaching to
DOWNSTREAM:0x7f4382c0f800
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:1578 Start
connecting to backend server
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:322
[DHTTP2:0x7f4382c2fc00] Using downstream address idx=0 out of 1
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:390
[DHTTP2:0x7f4382c2fc00] Connecting to downstream server
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_https_upstream.cc:395
[UPSTREAM:0x7f4382c720b0] HTTP request completed
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:1740
[DHTTP2:0x7f4382c2fc00] Connection established
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_connection.cc:418 tls:
handshake is still in progress
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_connection.cc:418 tls:
handshake is still in progress
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_connection.cc:418 tls:
handshake is still in progress
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_connection.cc:469 SSL/TLS
handshake completed
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:1841
[DHTTP2:0x7f4382c2fc00] SSL/TLS handshake completed
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_ssl.cc:1375 Update cache entry
for SSL_SESSION=0x7f4382ca3480, addr=192.168.56.111:443,
timestamp=1457675864.293091
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:1426
[DHTTP2:0x7f4382c2fc00] Negotiated next protocol: h2
10/Mar/2016:23:57:44 -0600 PID17624 [INFO]
shrpx_http2_downstream_connection.cc:438 [DCONN:0x7f4382c633c0] HTTP request
headers
:method: GET
:scheme: http
:path: /
host: 192.168.56.111
pragma: no-cache
cache-control: no-cache
accept:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/48.0.2564.109 Safari/537.36
accept-encoding: gzip, deflate, sdch
accept-language: en-US,en;q=0.8
x-forwarded-host: 192.168.56.120
x-forwarded-server: www.example.com
x-forwarded-for: 192.168.56.115
x-forwarded-proto: http
via: 1.1 nghttpx

10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:734
[DHTTP2:0x7f4382c2fc00] Stream stream_id=1 is being closed with error code 2
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:453
[CLIENT_HANDLER:0x7f4382cea000] Deleting
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_client_handler.cc:476
[CLIENT_HANDLER:0x7f4382cea000] Deleted
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_downstream.cc:157
[DOWNSTREAM:0x7f4382c0f800] Deleting
10/Mar/2016:23:57:44 -0600 PID17624 [INFO]
shrpx_http2_downstream_connection.cc:56 [DCONN:0x7f4382c633c0] Deleting
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_http2_session.cc:639
[DHTTP2:0x7f4382c2fc00] Remove downstream
10/Mar/2016:23:57:44 -0600 PID17624 [INFO]
shrpx_http2_downstream_connection.cc:89 [DCONN:0x7f4382c633c0] Deleted
10/Mar/2016:23:57:44 -0600 PID17624 [INFO] shrpx_downstream.cc:183
[DOWNSTREAM:0x7f4382c0f800] Deleted

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message