arduino/esp8266
1
0
Fork 0
mirror of https://github.com/esp8266/Arduino.git synced 2025-06-13 13:01:55 +03:00
Code Activity

Improve the compatibility of the doc between Github and RTD... (#4800)

Browse Source 
* Update requirements.txt

* Update conf.py

* Update libraries.rst

* Update libraries.rst

* Update libraries.rst

* Update stack_dump.rst

* Update client-examples.rst

* Update readme.rst

* Update readme.rst

* Update server-class.rst

* Update server-examples.rst

* Update soft-access-point-class.rst

* Update station-class.rst

* Update station-examples.rst

* Update udp-class.rst

* Update udp-examples.rst

* Update a04-board-generic-is-unknown.rst

* Update readme.rst

* Update readme.rst

* Update readme.rst
This commit is contained in:
ZaPpInG
2018-06-28 16:58:33 +02:00
committed by Develo
parent 0f34bd85d8
commit 1eb0645dcb
16 changed files with 40 additions and 72 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/esp8266wifi/server-examples.rst
View File

@ -223,8 +223,6 @@ Enter provided IP address in a web browser. You should see the page served by ES
.. figure:: pictures/server-browser-output.png
:alt: Output from server in a web browser
alt text
The page would be refreshed every 5 seconds. Each time this happens, you should see a request from the client (your web browser) printed out on the serial monitor:
::
@ -243,7 +241,7 @@ The page would be refreshed every 5 seconds. Each time this happens, you should
What Else?
~~~~~~~~~~
Looking on :doc:`client examples <client-examples>` you will quickly find out the similarities in protocol to the server. The protocol starts with a header that contains information what communication will be about. It contains what content type is communicated or accepted like ``text/html``. It states whether connection will be kept alive or closed after submission of the header. It contains identification of the sender like ``User-Agent: Mozilla/5.0 (Windows NT 6.1)``, etc.
Looking on `client examples <client-examples.rst>`__ you will quickly find out the similarities in protocol to the server. The protocol starts with a header that contains information what communication will be about. It contains what content type is communicated or accepted like ``text/html``. It states whether connection will be kept alive or closed after submission of the header. It contains identification of the sender like ``User-Agent: Mozilla/5.0 (Windows NT 6.1)``, etc.
Conclusion
~~~~~~~~~~
@ -252,4 +250,4 @@ The above example shows that a web server on ESP8266 can be set up in almost no
If you like to try another server example, check out `WiFiWebServer.ino <https://github.com/esp8266/Arduino/blob/master/libraries/ESP8266WiFi/examples/WiFiWebServer/WiFiWebServer.ino>`__, that provides functionality of toggling the GPIO pin on and off out of a web browser.
For the list of functions provided to implement and manage servers, please refer to the :doc:`Server Class <server-class>` documentation.
For the list of functions provided to implement and manage servers, please refer to the `Server Class <server-class.rst>`__ documentation.