Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP 1.0/1.1 support #228

Open
wader opened this issue Apr 13, 2022 · 0 comments
Open

HTTP 1.0/1.1 support #228

wader opened this issue Apr 13, 2022 · 0 comments
Labels
enhancement New feature or request new_format

Comments

@wader
Copy link
Owner

wader commented Apr 13, 2022

I've done some experiments with http 1.0/1.1 and there are some things to consider:

  • How to deal with white space/line separator. Own fields or bake into next/prev field?
  • Support header line folding? (multi-line headers)
  • How to represent multiple request/responses, root is always an array of structs?
  • Decode body. Introduce a "content-type" group to let other decoders probe mime?
  • De-chunking.
  • Range-requests.
  • Content-Encoding.
  • Transfer-Encoding.
  • Separate multi-part decoder, pass long content-type for decoding.
  • How to get good test data. Done som promising experiments generating input files using caddy and curl --trace and some adhoc fq scripts
  • How to pass options in combination with passing content-type options etc?

Hopefully a future http2/3 decoders can reuse same decode structure.

@wader wader added enhancement New feature or request new_format labels Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new_format
Projects
None yet
Development

No branches or pull requests

1 participant