❓
물음표살인마 블로그
  • README
  • ALGORITHM
    • Sieve of Eratosthenes
    • Round Up
    • Binary Search
    • Union Find
    • Sorting Array
    • Lcm, Gcd
  • TechTalk Review
    • Template
  • Books
    • CS Note for Interview
      • Ch1. Design Pattern & Programming paradigm
        • 1.1.1 Singleton Pattern
        • 1.1.2 Factory Pattern
        • 1.1.4 Observer Pattern
        • 1.1.5 Proxty Pattern & Proxy Server
        • 1.1.8 Model-View-Controller Pattern
        • 1.2.1 Declarative and Functional Programming
        • 1.2.2 Object Oriented Programming
      • Ch2. Network
        • 2.2.1 TCP/IP Four-Layer Model
        • 2.2.1-1 TCP 3, 4 way handshake
        • 2.3 Network Devices L4, L7
        • 2.4.1 ARP, RARP
        • 2.4.2 Hop By Hop Communication
        • 2.4.3 IP Addressing Scheme
      • Ch3. Operating System
        • 3.1.1 Roles and Structure of Operating Systems
        • 3.2.1 Memory Hierarchy
        • 3.2.2 Memory Management
        • 3.3.1 Processes and Compilation Process
        • 3.3.3 Memory Structure of a Process
        • 3.3.4 Process Control Block (PCB)
        • 3.3.5 Multiprocessing
        • 3.3.6 Threads and Multithreading
        • 3.3.7 Shared Resources and Critical Sections
        • 3.3.8 Deadlock
        • 3.4 CPU Scheduling Algorithm
      • Ch4. Database
        • 4.1 Database Basic
        • 4.2 Normalization
        • 4.3 Transaction and Integrity
        • 4.4 Types of Databases
        • 4.5 Indexes
        • 4.6 Types of Joins
        • 4.7 Principles of Joins
      • Ch5. Data Structure
    • Learning the Basics of Large-Scale System Design through Virtual Interview Cases
      • 1. Scalability based on user counts(1/2)
      • 1. Scalability based on user counts(2/2)
      • 2.Back-of-the-envelope estimation
      • 3. Strategies for System Design Interviews
      • 4. Rate Limiter
      • 5. Consistent Hashing
      • 6. Key-Value System Design
      • 7. Designing a Unique ID Generator for Distributed Systems
      • 8. Designing a URL Shortener
      • 9. Designing a Web Crawler
      • 10. Notification System Design
      • 11. Designing a News Feed System
      • 12. Chat System Design
      • 13. AutoComplete
      • 14. Design YouTube
      • 15. Design Google Drive
      • Loadbalancer Algorithms
      • Cache tier
      • CDN, Content Delivery Network
      • Stateless Web tier
    • Computer System A programmer's perspective
    • Effective Java
      • Item 1. Consider Static Factory Methods Instead of Constructors
      • Item 2. Consider a Builder When Faced with Many Constructor Parameters
      • Item 3. Ensure Singleton with Private Constructor or Enum Type
      • Item 4. Enforce Noninstantiability with a Private Constructor
      • Item 5. Prefer Dependency Injection to Hardwiring Resources
      • Item 6. Avoid Creating Unnecessary Objects
      • Item 7. Eliminate Obsolete Object References
      • Item 8. Avoid Finalizers and Cleaners
      • Item 9.Prefer try-with-resources to try-finally
      • Item10. Adhering to General Rules When Overriding equals
        • Handling Transitivity Issues
        • Ensuring Consistency
      • Item11. Override hashCode When You Override equals
      • Item12. Always Override toString
        • Always Override toString
      • Item13. Override Clone Judiciously
      • Item14. Consider Implementing Comparable
      • Item15. Minimize the Accessibility of Classes and Members
      • Item16. Accessor Methods Over Public Fields
      • Item17. Minimize Mutability
      • Item18. Composition over inherentance
      • Item19. Design and Document for Inheritance, or Else Prohibit It
      • Item20. Prefer Interfaces to Abstract Classes
      • Item21. Design Interfaces with Implementations in Mind
      • Item22. Use Interfaces Only to define Types
      • Item23. Prefer Class Hierarchies to Tagged Classes
      • Item24. Favor Static Member Classes Over Non-Static
      • Item28. Use Lists Instead of Arrays
      • Item29. Prefer Generic Types
      • Item30. Favor Generic Methods
    • Head First Design Patterns
      • Ch1. Strategy Pattern
      • Ch2. Observer Pattern
        • Ver1. Ch2. Observer Pattern
      • Ch3. Decorator Pattern
        • Ch3. Decorator Pattern
      • Ch4. Factory Pattern
      • Ch5. Singleton Pattern
      • Ch6. Command Pattern
      • Ch7. Adapter and Facade Pattern
      • Ch8. Template Method Pattern
    • Digging Deep into JVM
      • Chapter 2. Java Memory Area & Memory Overflow
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (1/2)
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (2/2)
      • Chapter 5. Optimization Practice
      • Chapter 6. Class file structure
      • Chapter 8. Bytecode Executor Engine (1/2)
  • Interview Practices
    • Restful API Practices
      • Url Shortener API
      • Event Ticket Reservation API
      • Course Management API
      • Search posts by tags API
      • Online Code platform API
      • Simple Task Management API
      • Event Participation API
      • Review System API
      • Car management API
      • Online Library
    • Tech Review
      • if(kakao)
        • Kakao Account Cache Migration / if(kakao)2022
        • Improving the Anomaly Detection System for KakaoTalk Messaging Metrics / if(kakao) 2022
        • Standardizing API Case Handling Without Redeployment / if(kakaoAI)2024
        • JVM warm up / if(kakao)2022
    • Naver Computer Science
      • Process & Thread
      • TCP & UDP
      • Spring & Servlet
      • Filter & Interceptor & AOP
      • Equals() & ==
      • Dependency Injection
      • Object Oriented Programming
  • F-Lab
    • Week1
      • Client & Server
      • HTTP
      • TCP/UDP
      • REST API
      • Questions
        • Object Oriented Programming
        • HTTP
        • Process & Thread
        • Data Structure
    • Week2
      • OSI 7 layer
      • Web vs WAS
    • Week3
      • RDB vs NoSQL
      • RDB Index
      • Cache
      • Redis
      • Messaging Queue
    • Week4
      • Project - Ecommerce
    • Week5
      • ERD - 1
    • Week6
      • Ecommerce - 2
      • Role
      • pw hashing && Salt
      • CreatedAt, ModifiedAt
      • JWT
      • Copy of ERD - 1
    • Week7
      • Vault (HashiCorp Vault)
    • Week 8
      • Api Endpoints
    • Week10
      • Product Create Workflow
  • TOY Project
    • CodeMentor
      • Implementation of Kafka
      • Project Improvement (Architectural Enhancements)
      • Communication between servers in msa
  • JAVA
    • MESI protocol in CAS
    • CAS (Compare and Set)
    • BlockingQueue
    • Producer & Consumer
    • Synchronized && ReentrantLock
    • Memory Visibility
    • Checked vs Unchecked Exception
    • Thread
    • Batch delete instead of Cascade
    • Java Questions
      • Week 1(1/2) - Basic Java
      • Week 1(2/2) - OOP
      • Week 2(1/2) - String, Exception, Generic
      • Week2(2/2) Lambda, Stream, Annotation, Reflection
      • Week3(1/2) Collections
      • Week3(2/2) Threads
      • Week4 Java Concurrency Programming
      • Week5 JVM & GC
    • Java 101
      • JVM Structure
      • Java Compiles and Execution Method
      • Override, Overload
      • Interface vs Abstract Class
      • Primitive vs Object Type
      • Identity and equality
      • String, StringBuilder, StringBuffer
      • Checked Exceptions and Unchecked Exceptions
      • Java 8 methods
      • Try-with-reources
      • Strong Coupling and Loose Coupling
      • Serialization and Deserialization
      • Concurrency Programming in Java
      • Mutable vs Immutable
      • JDK vs JRE
  • SPRING
    • DIP. Dependency Inversion Principal
    • Ioc container, di practice
    • @Transactional
    • Proxy Pattern
    • Strategy Pattern
    • Template Method Pattern
    • using profile name as variable
    • Spring Questions
      • Spring Framework
      • Spring MVC & Web Request
      • AOP (Aspect-Oriented Programming)
      • Spring Boot
      • ORM & Data Access
      • Security
      • ETC
  • DATABASE
    • Enhancing Query Performance & Stability - User list
    • Ensuring Data Consistency, Atomicity and UX Optimization (feat.Firebase)
    • Redis: Remote Dictionary Server
    • Database Questions
      • Week1 DBMS, RDBMS basics
      • Week2 SQL
      • Week3 Index
      • Week4 Anomaly, Functional Dependency, Normalization
      • Week5 DB Transaction, Recovery
    • Normalization
      • 1st Normal Form
      • 2nd Normal Form
      • 3rd Normal Form
  • NETWORK
    • HTTP & TCP head of line blocking
    • HTTP 0.9-3.0
    • Blocking, NonBlocking and Sync, Async
    • Network Questions
      • Week1 Computer Network Basic
      • Week2(1/3) Application Layer Protocol - HTTP
      • Week2(2/3) Application Layer Protocol - HTTPS
      • Week2(3/3) Application Layer Protocol - DNS
      • Week3 Application Layer
      • Week4 Transport Layer - UDP, TCP
      • Week5 Network Layer - IP Protocol
    • Network 101
      • https://www.google.com
      • TCP vs UDP
      • Http vs Https
      • TLS Handshake 1.2
      • HTTP Method
      • CORS & SOP
      • Web Server Software
  • OS
    • Operating System Questions
      • Week1 OS & How Computer Systems Work
      • Week2(1/2) Process
      • Week2(2/2) Thread
      • Week3 CPU Scheduling
      • Week4 Process Synchronize
      • Week5 Virtual Memory
    • Operating System 101
      • Operating system
        • The role of the operating system
        • The composition of the operating system.
      • Process
        • In Linux, are all processes except the initial process child processes?
        • Zombie process, orphan process
        • (Linux) Daemon process
        • Process address space
        • Where are uninitialized variables stored?
        • Determination of the size of the Stack and Heap
        • Access speed of Stack vs Heap
        • Reason for memory space partitioning
        • Process of compiling a process
        • sudo kill -9 $CURRENT_PID
      • Thread
        • Composition of a thread's address space
      • Process vs Thread
        • Creation of processes and threads in Linux
      • Multiprocessing
        • Web Browser
        • Implementation of multiprocessing
        • Application areas of multiprocessing
      • Multithreading
        • Application areas of multithreading
      • Interrupt
        • HW / SW Interrupt
        • Method of handling interrupts
        • Occurrence of two or more interrupts simultaneously
      • Polling
      • Dual Mode
        • Reason for distinguishing between user mode and kernel mode
      • System call
        • Differentiation between system calls
        • Types of system calls
        • Execution process of a system call
      • Process Control Block (PCB)
        • PCB의 구조
        • 쓰레드는 PCB를 갖고 있을까?
        • 프로세스 메모리 구조
      • Context switching
        • Timing of context switching
        • Registers saved during context switching
        • Context switching in processes
        • Context switching in threads
        • Difference between context switching in processes and threads
        • Information of the current process during context switching
      • Interprocess Communication (IPC)
        • Cases where IPC is used
        • Process address space in IPC Shared Memory technique
        • Types of IPC
  • COMPUTER SCIENCE
    • Computer Architecture 101
      • 3 components of a computer
      • RAM vs ROM
      • CPU vs GPU
      • SIMD
      • Two's complement
      • Harvard Architecture vs. von Neumann Architecture
      • The structure of a CPU.
      • Instruction cycle (CPU operation method)
      • Instruction pipelining
      • Bus
      • Memory area
      • Memory hierarchy structure
        • Reason for using memory hierarchy structure
      • Cache memory
      • L1, L2, L3 Cache
      • Locality of reference (cache)
      • Fixed-point vs Floating-point
        • epresentation of infinity and NaN (Not a Number) in floating-point
      • RISC vs CISC
      • Hamming code
      • Compiler
      • Linking
      • Compiler vs Interpreter
      • Mutex vs Semaphore
      • 32bit CPU and 64bit CPU
      • Local vs Static Variable
      • Page
  • Programming Paradigm
    • Declarative vs Imperative
  • JPA, QueryDsl
    • why fetchResults() is deprecated
  • PYTHON
    • Icecream
  • FASTAPI
    • Template Page
  • LINUX
    • Template Page
  • DATA STRUCTURE
    • Counting Sort
    • Array vs Linked List
  • GIT, Github
    • git clone, invalid path error
  • INFRA
    • Template Page
  • AWS
    • Server Log Archive Pipeline
    • Image Processing using Lambda
  • DOCKER
    • Docker and VM
    • Python Executable Environment
    • Docker commands
  • docker-compose
    • Kafka, Multi Broker
  • KUBERNATES
    • !Encountered Errors
      • my-sql restarts
      • kafka producer: disconnected
    • Kubernetes Components
    • Helm
      • Helm commands
    • Pod network
    • Service network
      • deployment.yaml
      • services.yaml
    • Service type
      • Cluster IP
      • NodePort
    • service-name-headless?
    • kube-proxy
  • GraphQL
    • Template Page
  • WEB
    • Template Page
  • Reviews
    • Graphic Intern Review
    • Kakao Brain Pathfinder Review
    • JSCODE 자바 1기 Review
  • 😁Dev Jokes
    • Image
      • Plot twist
      • Priorities
      • SQL join guide
      • Google is generous
      • Genie dislikes cloud
      • buggy bugs
      • last day of unpaid internship
      • what if clients know how to inspect
      • its just game
      • how i wrote my achievement on resume
      • self explanatory
      • chr(sum(range(ord(min(str(not))))))
Powered by GitBook
On this page
  • 1. 정의
  • 2. 특징
  • 3. 구조
  • 3.1. 요청 구조
  • 3.2. 응답 구조
  • 4. 메서드
  • 4.1. GET
  • 4.2. POST
  • 4.3. PUT
  • 4.4. PATCH
  • 5. 상태 코드
  • 2XX 성공
  • 3XX 리다이렉션
  • 4XX 클라이언트 오류
  • 5XX 서버 오류
  • 6. 버전
  • 1.0
  • 1.1
  • 2.0
  • 3.0 QUIC
  • 10. 단점과 해결 방법
  1. F-Lab
  2. Week1

HTTP

1. 정의

  • HTTP(Hypertext Transfer Protocol)은 애플리케이션 계층 프로토콜.

  • 클라이언트와 서버간의 데이터를 주고 받기 위해 사용

  • HTML, JSON, 이미지 등 다양한 형식 데이터를 전송

2. 특징

  • 텍스트 기반 프로토콜: 사람이 읽을 수 있는 텍스트 형식으로 작성됩니다.

  • Stateless: 이전 요청 상태를 기억하지 않음. 매 요청마다 쿠키/토큰을 사용하거나 세션을 사용

  • 클라이언트-서버 모델: 클라이언트가 요청을 보내고 서버가 응답을 반환.

  • 확장성: 다양한 데이터 형식(JSON, HTML, XML 등)을 지원하며, API개발에도 사용

3. 구조

3.1. 요청 구조

  1. 요청 라인: 요청의 핵심 정보를 포함. (GET /index.html HTTP/1.1)

  2. 헤더: 요청의 부가 정보 포함. (Host: www.example.com User-Agent: Mozilla/5.0)

  3. 본문: POST, PUT 등 메서드에서 서버로 전송되는 데이터가 포함.

3.2. 응답 구조

  1. 상태 라인: 서버의 처리 결과를 나타냄. (HTTP/1.1 200 OK)

  2. 헤더: 응답 부가 정보 포함. (Content-Type: text/html)

  3. 본문: 서버가 전달하는 실제 데이터. (HTML, JSON, 이미지)

4. 메서드

4.1. GET

  • 리소스 조회

  • 멱등. 캐싱 가능

  • 리소스를 변경하지 않는 안전한 메서드

4.2. POST

  • 새로운 데이터를 전송하거나 생성할때 사용

  • 멱등하지 않음. 캐싱 불가능

  • 리소스 변경으로 안전하지 않음

4.3. PUT

  • 데이터를 전체적으로 교체할때 사용

  • 멱등. 데이터를 덮어쓰는 경우

4.4. PATCH

  • 데이터를 일부만 수정할때 사용

  • 멱등하지 않을수도 있음. (+1 같은 경우)

멱등:

  • 안정성 및 오류 처리: 네트워크 오류로 여러번 요청을 보내더라도 문제 없음.

  • 안전한 재시도 로직 구현: 요청 재시도로 여러개의 요청을 보내도 문제 없음.

  • 캐싱과 성능 최적화: 서버나 프록시에서 캐싱이 용이. 결과를 재생성하지 않아도 됨.

  • 분산 시스템에서의 일관성 유지: 분산 시스템에서는 요청이 중복으로 처리될 가능성이 있음.

  • 서비스 안정성: 서비스 장애 시 복구 과정에서 멱등한 요청은 중복된 작업을 수행하더라도 안전함.

5. 상태 코드

2XX 성공

  • 200 OK: 요청 성공

  • 201 Created: 리소스 생성 성공

3XX 리다이렉션

  • 301 Moved Permanently: 리소스가 영구적으로 이동됨. 클라이언트는 새로운 URL을 캐싱하여, 요청시 항상 새 URL로 요청

  • 302 Found: 리소스가 임시로 이동됨. 클라이언트는 새 URL로 이동하지만, 기존 URL에 계속 요청함.

4XX 클라이언트 오류

  • 400 Bad Request: 잘못된 요청

  • 404 Not Found: 요청한 리소스를 찾을 수 없음

5XX 서버 오류

  • 500 Internal Server Error: 서버에서 처리 중 오류 발생

  • 503 Service Unavailable: 서버가 현재 처리 불가능

6. 버전

1.0

  • 헤더

  • 상태 코드

  • GET외의 메서드

  • Stop and Wait Protocol

1.1

  • Keep-Alive

  • 파이프라이닝: 연속적으로 여러 요청을 보냄. 하지만 응답은 순서대로 받아야함. 요청 자체로 인한 HOL Blocking.

  • Chunk Transfer

  • Etag Caching

2.0

  • Binary Framing Layer: 요청 응답을 이진 형식으로 변환, 헤더와 데이터를 프레임으로 쪼갬(프레임 독립성)

  • 멀티플랙싱: TCP연결에서 스트림채널을 열어, 여러 HTTP 요청/응답을 병렬로 전송. TCP 패킷 손실로 인한 HOL Blocking.

  • Stream Prioritization: 요청에 대한 우선순위 부여

  • Server Push: 요청이 없거나 하나의 요청에 대해 여러 응답 가능

  • HPack Compression: 과거 요청 헤더를 기억하고 압축 가능

3.0 QUIC

  • 패킷 손실 복구(SACK, Selective Ack): 받지 못한 패킷에 대해서만 Ack를 보내어 신뢰성 확보.

  • 0-RTT: 이전 연결 정보를 저장합니다. 첫 연결 종료시 서버의 세션 티켓, 사전 공유 키(PSK)를 저장합니다. 두 번쨰 연결시, 이를 재활용하여 요청 데이터와 함께 보냅니다. 서버는 세션 티켓을 검증하고, PSK를 사용해 암호화 키를 설정하고 클라이언트 요청을 처리합니다. 서버는 핸드쉐이크 완료 메세지를 보내고, 데이터를 클라이언트에 전송합니다.

  • 스트림 독립성: 각 패킷이 어느 요청의 것(스트림)인지 명시적으로 구분하여 독립적으로 관리되도록 함. 멀티플랙싱의 HOL blocking 문제를 해결.

  • 헤더 압축: QPack을 사용. Hpack보다 헤더 크기가 줄어듬

Pipelining Head-Of-Line Blocking

요청이 순차적으로 처리되기 때문에, 앞선 요청이 지연되면 뒤따르는 요청도 지연.

Multiplexing Head-Of-Line Blocking

상황:

요청1의 패킷1,2,3 요청2의 패킷1,2,3 요청3의 패킷1,2,3 이 있는 상황에서, 요청 2의 패킷 2가 손상됬을때, 나머지 요청들의 처리가 차단.

수신측에서는 손실된 패킷이 요청2의 패킷이라는걸 모르기때문에 기다리는 것

10. 단점과 해결 방법

  • 무상태성 -> 쿠키, 세션, JWT 사용

  • 보안 문제 -> HTTPS 도입

  • 성능 문제 -> HTTP/2, HTTP/3 도입

PreviousClient & ServerNextTCP/UDP

Last updated 4 months ago