remove toc for now
This commit is contained in:
parent
934937bcb4
commit
5f062c7bc3
57
README.md
57
README.md
|
@ -7,63 +7,6 @@ Async HTTP and WebSocket Server for ESP8266 Arduino
|
|||
Requires [ESPAsyncTCP](https://github.com/me-no-dev/ESPAsyncTCP) to work
|
||||
To use this library you might need to have the latest git versions of [ESP8266](https://github.com/esp8266/Arduino) Arduino Core
|
||||
|
||||
- Table of Contents
|
||||
- [Why should you care](#)
|
||||
- [Important things to remember](#)
|
||||
- [Principles of operation](#)
|
||||
- [The Async Web server](#)
|
||||
- [Request Life Cycle](#)
|
||||
- [Rewrites and how do they work](#)
|
||||
- [Handlers and how do they work](#)
|
||||
- [Responses and how do they work](#)
|
||||
- [Libraries and projects that use AsyncWebServer](#)
|
||||
- [Request Variables](#)
|
||||
- [Common Variables](#)
|
||||
- [Headers](#)
|
||||
- [GET, POST and FILE parameters](#)
|
||||
- [FILE Upload handling](#)
|
||||
- [Body data handling](#)
|
||||
- [Responses](#)
|
||||
- [Redirect to another URL](#)
|
||||
- [Basic response with HTTP Code](#)
|
||||
- [Basic response with HTTP Code and extra headers](#)
|
||||
- [Basic response with string content](#)
|
||||
- [Basic response with string content and extra headers](#)
|
||||
- [Send large webpage from PROGMEM](#)
|
||||
- [Send large webpage from PROGMEM and extra headers](#)
|
||||
- [Send binary content from PROGMEM](#)
|
||||
- [Respond with content coming from a Stream](#)
|
||||
- [Respond with content coming from a Stream and extra headers](#)
|
||||
- [Respond with content coming from a File](#)
|
||||
- [Respond with content coming from a File and extra headers](#)
|
||||
- [Respond with content using a callback](#)
|
||||
- [Respond with content using a callback and extra headers](#)
|
||||
- [Chunked Response](#)
|
||||
- [Print to response](#)
|
||||
- [ArduinoJson Basic Response](#)
|
||||
- [ArduinoJson Advanced Response](#)
|
||||
- [Serving static files](#)
|
||||
- [Serving specific file by name](#)
|
||||
- [Serving files in directory](#)
|
||||
- [Specifying Cache-Control header](#)
|
||||
- [Specifying Date-Modified header](#)
|
||||
- [Using filters](#)
|
||||
- [Serve different site files in AP mode](#)
|
||||
- [Rewrite to different index on AP](#)
|
||||
- [Serving different hosts](#)
|
||||
- [Bad Responses](#)
|
||||
- [Respond with content using a callback without content length to HTTP/1.0 clients](#)
|
||||
- [Async WebSocket Plugin](#)
|
||||
- [Async WebSocket Event](#)
|
||||
- [Methods for sending data to a socket client](#)
|
||||
- [Async Event Source Plugin](#)
|
||||
- [Setup Event Source on the server](#)
|
||||
- [Setup Event Source in the browser](#)
|
||||
- [Scanning for available WiFi Networks](#)
|
||||
- [Remove handlers and rewriters](#)
|
||||
- [Setting up the server](#)
|
||||
- [Methods for controlling websocket connections](#)
|
||||
|
||||
## Why should you care
|
||||
- Using asynchronous network means that you can handle more than one connection at the same time
|
||||
- You are called once the request is ready and parsed
|
||||
|
|
Loading…
Reference in New Issue