Function assign_headers

modules/http2/h2_request.c:319–372

#endif

static void assign_headers(request_rec *r, const h2_request *req,
                           int no_body, int is_connect)
{
    const char *cl;

    r->headers_in = apr_table_clone(r->pool, req->headers);

    if (req->authority && !is_connect) {
        /* for internal handling, we have to simulate that :authority
         * came in as Host:, RFC 9113 ch. says that mismatches between
         * :authority and Host: SHOULD be rejected as malformed. However,
         * we are more lenient and just replace any Host: if we have
         * an :authority.
         */
        const char *orig_host = apr_table_get(req->headers, "Host");
        if (orig_host && strcmp(req->authority, orig_host)) {
            ap_log_rerror(APLOG_MARK, APLOG_DEBUG, 0, r, APLOGNO(10401)
                          "overwriting 'Host: %s' with :authority: %s'",
                          orig_host, req->authority);
            apr_table_setn(r->subprocess_env, "H2_ORIGINAL_HOST", orig_host);
        }
        apr_table_setn(r->headers_in, "Host", req->authority);
        ap_log_rerror(APLOG_MARK, APLOG_TRACE1, 0, r,
                      "set 'Host: %s' from :authority", req->authority);
    }

    /* Unless we open a byte stream via CONNECT, apply content-length guards. */
    if (!is_connect) {
        cl = apr_table_get(req->headers, "Content-Length");
        if (no_body) {
            if (!cl && apr_table_get(req->headers, "Content-Type")) {
                /* If we have a content-type, but already seen eos, no more
                 * data will come. Signal a zero content length explicitly.
                 */
                apr_table_setn(req->headers, "Content-Length", "0");
            }
        }
#if !AP_HAS_RESPONSE_BUCKETS
        else if (!cl) {
            /* there may be a body and we have internal HTTP/1.1 processing.
             * If the Content-Length is unspecified, we MUST simulate
             * chunked Transfer-Encoding.
             *
             * HTTP/2 does not need a Content-Length for framing. Ideally
             * all clients set the EOS flag on the header frame if they
             * do not intent to send a body. However, forwarding proxies
             * might just no know at the time and send an empty DATA
             * frame with EOS much later.
             */
            apr_table_mergen(r->headers_in, "Transfer-Encoding", "chunked");
        }
#endif /* else AP_HAS_RESPONSE_BUCKETS */
  }
}

request_rec *h2_create_request_rec(const h2_request *req, conn_rec *c,
                                   int no_body)