<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network on Blowing in the wind</title>
    <link>https://zheng-bobo.github.io/en/categories/network/</link>
    <description>Recent content in Network on Blowing in the wind</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 11 Feb 2021 09:45:47 +0800</lastBuildDate>

  <atom:link href="https://zheng-bobo.github.io/en/categories/network/index.xml" rel="self" type="application/rss+xml" />


    <item>
      <title>Translation: Linux I/O Multiplexing - select vs. poll vs. epoll</title>
      <link>https://zheng-bobo.github.io/en/post/linux-io-multiplexing-select-poll-epoll/</link>
      <pubDate>Thu, 11 Feb 2021 09:45:47 +0800</pubDate>

      <guid>https://zheng-bobo.github.io/en/post/linux-io-multiplexing-select-poll-epoll/</guid>
      <description>Introduction  Before reading this article, you can first understand the five I/O models of Liunx
 References: I/O Models &amp;ndash;Section 6.2 of &amp;ldquo;UNIX® Network Programming Volume 1, Third Edition: The Sockets Networking&amp;rdquo; by Richard Stevens
The following is the text of the article    One of the basic concepts of Linux (actually Unix) is that everything in Unix/Linux is a file. Each process has a file descriptor table that points to files, sockets, devices, and other operating system objects related to the process.</description>
    </item>

    <item>
      <title>Introduction to CSRF and CORS</title>
      <link>https://zheng-bobo.github.io/en/todo/csrf-and-cors-introduction/</link>
      <pubDate>Thu, 04 Feb 2021 17:32:47 +0800</pubDate>

      <guid>https://zheng-bobo.github.io/en/todo/csrf-and-cors-introduction/</guid>
      <description>Introduction  Before introducing CRSF(Cross-site request forgery)&amp;amp;CORS(Cross-origin resource sharing), we first introduce HTTP. If readers are familiar with HTTP, they can skip this content directly.
HTTP request ﻿An HTTP request consists of four parts: request line, request header, blank line and request body.
1 2 3 4 5 6 7  GET /mix/76.html?name=kelvin&amp;amp;password=123456 HTTP/1.1 Host: www.fishbay.cn Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.</description>
    </item>

    <item>
      <title>HTTP/1.1 vs. HTTP/2</title>
      <link>https://zheng-bobo.github.io/en/post/http-1-1-vs-http-2/</link>
      <pubDate>Thu, 16 Jan 2020 10:25:00 +0800</pubDate>

      <guid>https://zheng-bobo.github.io/en/post/http-1-1-vs-http-2/</guid>
      <description>HTTP 1.1 In January 1997, HTTP/1.1 version was released, only half a year later than version 1.0. It further improved the HTTP protocol and has been used to this day 20 years later, and is still the most popular version. Main optimization points:
 Support long connection by default  HTTP/1.1 supports persistent connections and request pipelining. Persistent connections reuse established TCP connections and avoid repeating the RTT cost of the three-way handshake.</description>
    </item>

  </channel>
</rss>