Tarantool development patches archive
 help / color / mirror / Atom feed
From: Ilya Markov <imarkov@tarantool.org>
To: georgy@tarantool.org
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] [http.client 0/2] Fix parsing headers
Date: Fri, 15 Jun 2018 17:24:09 +0300	[thread overview]
Message-ID: <cover.1529072604.git.imarkov@tarantool.org> (raw)



Ilya Markov (2):
  http: Remove parsed status line from headers
  http: Fix parse long headers names

branch: gh-3451-http-client-bad-headers-parse

 src/http_parser.c                 | 81 ++++++++++++++++++++++++++-------------
 src/http_parser.h                 | 14 ++++---
 src/lua/httpc.c                   | 45 ++++++++++++++--------
 test/app-tap/http_client.test.lua |  9 ++++-
 test/app-tap/httpd.py             |  1 +
 5 files changed, 102 insertions(+), 48 deletions(-)

-- 
2.7.4

             reply	other threads:[~2018-06-15 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 14:24 Ilya Markov [this message]
2018-06-15 14:24 ` [tarantool-patches] [http.client 1/2] http: Remove parsed status line from headers Ilya Markov
2018-06-15 14:24 ` [tarantool-patches] [http.client 2/2] http: Fix parse long headers names Ilya Markov

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=cover.1529072604.git.imarkov@tarantool.org \
    --to=imarkov@tarantool.org \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [http.client 0/2] Fix parsing headers' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox