introduction.asciidoc 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556
  1. [[introduction]]
  2. == Introduction
  3. Cowboy is a small, fast and modular HTTP server written in Erlang.
  4. Cowboy aims to provide a complete HTTP stack, including its derivatives
  5. Websocket and REST. Cowboy currently supports HTTP/1.0, HTTP/1.1, HTTP/2,
  6. Websocket (all implemented drafts + standard) and Webmachine-based REST.
  7. Cowboy is a high quality project. It has a small code base, is very
  8. efficient (both in latency and memory use) and can easily be embedded
  9. in another application.
  10. Cowboy is clean Erlang code. It includes hundreds of tests and its code
  11. is fully compliant with the Dialyzer. It is also well documented and
  12. features both a Function Reference and a User Guide.
  13. === Prerequisites
  14. Beginner Erlang knowledge is recommended for reading this guide.
  15. Knowledge of the HTTP protocol is recommended but not required, as it
  16. will be detailed throughout the guide.
  17. === Supported platforms
  18. Cowboy is tested and supported on Linux.
  19. Cowboy has been reported to work on other platforms, but we make no
  20. guarantee that the experience will be safe and smooth. You are advised
  21. to perform the necessary testing and security audits prior to deploying
  22. on other platforms.
  23. Cowboy is developed for Erlang/OTP 17.0, 17.1.2 and 17.3. By the time
  24. this branch gets released the target version will probably be 18.0 and
  25. above.
  26. Cowboy may be compiled on other Erlang versions with small source code
  27. modifications but there is no guarantee that it will work as expected.
  28. Cowboy uses the maps data type which was introduced in Erlang 17.0.
  29. === Versioning
  30. Cowboy uses http://semver.org/[Semantic Versioning 2.0.0].
  31. === Conventions
  32. In the HTTP protocol, the method name is case sensitive. All standard
  33. method names are uppercase.
  34. Header names are case insensitive. Cowboy converts all the request
  35. header names to lowercase, and expects your application to provide
  36. lowercase header names in the response.
  37. The same applies to any other case insensitive value.