Explain HTTP message (2) - how web container parses HTTP message

Abbot's temple 2020-11-13 05:41:10
explain http message web container


Abstract

stay Detailed explanation http message In the article , In detail http The text structure of the message . So as a server ,web How does the container parse http What about the message ? This article takes jetty and undertow Container as an example , Parsing web How does the container handle http The message .

We can learn from the overview in the previous article ,http A message is a regular string , So parse them , It's parsing strings , See if you are satisfied http The rules of the agreement .

start-line: Start line , Basic information describing the request or response
*( header-field CRLF ): head
CRLF
[message-body]: news body, Data actually transmitted

jetty

The following code is jetty9.4.12 edition

How to parse such a long string ,jetty It is realized by state machine . You can look at it org.eclipse.jetty.http.HttpParse class

 public enum State
{
START,
METHOD,
![](https://img-blog.csdnimg.cn/20191009220511890.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9mYW5nemhhbmcuYmxvZy5jc2RuLm5ldA==,size_16,color_FFFFFF,t_70),
SPACE1,
STATUS,
URI,
SPACE2,
REQUEST_VERSION,
REASON,
PROXY,
HEADER,
CONTENT,
EOF_CONTENT,
CHUNKED_CONTENT,
CHUNK_SIZE,
CHUNK_PARAMS,
CHUNK,
TRAILER,
END,
CLOSE, // The associated stream/endpoint should be closed
CLOSED // The associated stream/endpoint is at EOF
}

It's divided into 21 States , And then the flow of States . stay parseNext Method for the starting line -> header -> body content Resolve separately

public boolean parseNext(ByteBuffer buffer)
{
try
{
// Start a request/response
if (_state==State.START)
{
// Quick judgment
if (quickStart(buffer))
return true;
}
// Request/response line transformation
if (_state.ordinal()>= State.START.ordinal() && _state.ordinal()<State.HEADER.ordinal())
{
if (parseLine(buffer))
return true;
}
// headers transformation
if (_state== State.HEADER)
{
if (parseFields(buffer))
return true;
}
// content transformation
if (_state.ordinal()>= State.CONTENT.ordinal() && _state.ordinal()<State.TRAILER.ordinal())
{
// Handle HEAD response
if (_responseStatus>0 && _headResponse)
{
setState(State.END);
return handleContentMessage();
}
else
{
if (parseContent(buffer))
return true;
}
}
return false;
}

Overall process

As a whole, there are three paths

  1. Start -> start-line -> header -> end
  2. Start -> start-line -> header -> content -> end
  3. Start -> start-line -> header -> chunk-content -> end

Start line

start-line = request-line( Request start line )/( Response start line )status-line

  1. Request message parsing state migration
    Request line :START -> METHOD -> SPACE1 -> URI -> SPACE2 -> REQUEST_VERSION

  2. Response message parsing state migration
    Response line :START -> RESPONSE_VERSION -> SPACE1 -> STATUS -> SPACE2 -> REASON

header head

HEADER There is only one state , stay jetty There is also a distinction between HEADER_IN_NAM, HEADER_VALUE, HEADER_IN_VALUE etc. ,9.4 All of them have been removed . In order to improve the matching efficiency ,jetty Used Trie Tree quick match header head .

static
{
CACHE.put(new HttpField(HttpHeader.CONNECTION,HttpHeaderValue.CLOSE));
CACHE.put(new HttpField(HttpHeader.CONNECTION,HttpHeaderValue.KEEP_ALIVE));
// A lot of generalities are omitted below header head

content

Request body :

  1. CONTENT -> END, This is a normal belt Content-Length Header message ,HttpParser Has been running CONTENT state , Until the last ContentLength Reached the specified number , entering END state
  2. chunked Data transmitted in blocks
    CHUNKED_CONTENT -> CHUNK_SIZE -> CHUNK -> CHUNK_END -> END

undertow

undertow It's another kind of web Containers , How it's handled and jetty What's the difference
There are different kinds of state machines ,io.undertow.util.HttpString.ParseState

 public static final int VERB = 0;
public static final int PATH = 1;
public static final int PATH_PARAMETERS = 2;
public static final int QUERY_PARAMETERS = 3;
public static final int VERSION = 4;
public static final int AFTER_VERSION = 5;
public static final int HEADER = 6;
public static final int HEADER_VALUE = 7;
public static final int PARSE_COMPLETE = 8;

The specific processing flow is HttpRequestParser In an abstract class

public void handle(ByteBuffer buffer, final ParseState currentState, final HttpServerExchange builder) throws BadRequestException {
if (currentState.state == ParseState.VERB) {
//fast path, we assume that it will parse fully so we avoid all the if statements
// Rapid processing GET
final int position = buffer.position();
if (buffer.remaining() > 3
&& buffer.get(position) == 'G'
&& buffer.get(position 1) == 'E'
&& buffer.get(position 2) == 'T'
&& buffer.get(position 3) == ' ') {
buffer.position(position 4);
builder.setRequestMethod(Methods.GET);
currentState.state = ParseState.PATH;
} else {
try {
handleHttpVerb(buffer, currentState, builder);
} catch (IllegalArgumentException e) {
throw new BadRequestException(e);
}
}
// Handle path
handlePath(buffer, currentState, builder);
// Processing version
if (failed) {
handleHttpVersion(buffer, currentState, builder);
handleAfterVersion(buffer, currentState);
}
// Handle header
while (currentState.state != ParseState.PARSE_COMPLETE && buffer.hasRemaining()) {
handleHeader(buffer, currentState, builder);
if (currentState.state == ParseState.HEADER_VALUE) {
handleHeaderValue(buffer, currentState, builder);
}
}
return;
}
handleStateful(buffer, currentState, builder);
}

And jetty The difference is right content To deal with , stay header After processing , Place data in io.undertow.server.HttpServerExchange, Then according to the type , Different content Read mode , For example, deal with fixed length ,FixedLengthStreamSourceConduit.

Official account 【 Abbot's temple 】, The first time to receive an update of the article , Start the road of technical cultivation with the abbot
 Insert picture description here

Reference resources

http://www.blogjava.net/DLevin/archive/2014/04/19/411673.html

https://www.ph0ly.com/2018/10/06/jetty/connection/http-parser/

https://webtide.com/http-trailers-in-jetty/

http://undertow.io/undertow-docs/undertow-docs-2.0.0/

版权声明
本文为[Abbot's temple]所创,转载请带上原文链接,感谢

  1. [front end -- JavaScript] knowledge point (IV) -- memory leakage in the project (I)
  2. This mechanism in JS
  3. Vue 3.0 source code learning 1 --- rendering process of components
  4. Learning the realization of canvas and simple drawing
  5. gin里获取http请求过来的参数
  6. vue3的新特性
  7. Get the parameters from HTTP request in gin
  8. New features of vue3
  9. vue-cli 引入腾讯地图(最新 api,rocketmq原理面试
  10. Vue 学习笔记(3,免费Java高级工程师学习资源
  11. Vue 学习笔记(2,Java编程视频教程
  12. Vue cli introduces Tencent maps (the latest API, rocketmq)
  13. Vue learning notes (3, free Java senior engineer learning resources)
  14. Vue learning notes (2, Java programming video tutorial)
  15. 【Vue】—props属性
  16. 【Vue】—创建组件
  17. [Vue] - props attribute
  18. [Vue] - create component
  19. 浅谈vue响应式原理及发布订阅模式和观察者模式
  20. On Vue responsive principle, publish subscribe mode and observer mode
  21. 浅谈vue响应式原理及发布订阅模式和观察者模式
  22. On Vue responsive principle, publish subscribe mode and observer mode
  23. Xiaobai can understand it. It only takes 4 steps to solve the problem of Vue keep alive cache component
  24. Publish, subscribe and observer of design patterns
  25. Summary of common content added in ES6 + (II)
  26. No.8 Vue element admin learning (III) vuex learning and login method analysis
  27. Write a mini webpack project construction tool
  28. Shopping cart (front-end static page preparation)
  29. Introduction to the fluent platform
  30. Webpack5 cache
  31. The difference between drop-down box select option and datalist
  32. CSS review (III)
  33. Node.js学习笔记【七】
  34. Node.js learning notes [VII]
  35. Vue Router根据后台数据加载不同的组件(思考-&gt;实现-&gt;不止于实现)
  36. Vue router loads different components according to background data (thinking - & gt; Implementation - & gt; (more than implementation)
  37. 【JQuery框架,Java编程教程视频下载
  38. [jQuery framework, Java programming tutorial video download
  39. Vue Router根据后台数据加载不同的组件(思考-&gt;实现-&gt;不止于实现)
  40. Vue router loads different components according to background data (thinking - & gt; Implementation - & gt; (more than implementation)
  41. 【Vue,阿里P8大佬亲自教你
  42. 【Vue基础知识总结 5,字节跳动算法工程师面试经验
  43. [Vue, Ali P8 teaches you personally
  44. [Vue basic knowledge summary 5. Interview experience of byte beating Algorithm Engineer
  45. 【问题记录】- 谷歌浏览器 Html生成PDF
  46. [problem record] - PDF generated by Google browser HTML
  47. 【问题记录】- 谷歌浏览器 Html生成PDF
  48. [problem record] - PDF generated by Google browser HTML
  49. 【JavaScript】查漏补缺 —数组中reduce()方法
  50. [JavaScript] leak checking and defect filling - reduce() method in array
  51. 【重识 HTML (3),350道Java面试真题分享
  52. 【重识 HTML (2),Java并发编程必会的多线程你竟然还不会
  53. 【重识 HTML (1),二本Java小菜鸟4面字节跳动被秒成渣渣
  54. [re recognize HTML (3) and share 350 real Java interview questions
  55. [re recognize HTML (2). Multithreading is a must for Java Concurrent Programming. How dare you not
  56. [re recognize HTML (1), two Java rookies' 4-sided bytes beat and become slag in seconds
  57. 【重识 HTML ,nginx面试题阿里
  58. 【重识 HTML (4),ELK原来这么简单
  59. [re recognize HTML, nginx interview questions]
  60. [re recognize HTML (4). Elk is so simple