commit | 5d99cc309283802d5d49b60f7d6bb0dd7a522a0e | [log] [tgz] |
---|---|---|
author | Samuel Shuert <coded@clicks.codes> | Wed Jan 10 17:27:57 2024 -0500 |
committer | Samuel Shuert <coded@clicks.codes> | Thu Jan 11 21:04:54 2024 +0000 |
tree | 7800dd9a2e8d6198e27bd77f918f13c8b1c0db4f | |
parent | aa5fa6c53ad1748b8eab8a1524d0370a20e9b3e3 [diff] |
Add Getting files from the server Change-Id: I1904d419bef4c549fb34e0340f96387416adaab0 Reviewed-on: https://git.clicks.codes/c/Clicks/BYO/HttpServer/rust/+/266 Tested-by: Skyler Grey <minion@clicks.codes> Reviewed-by: Samuel Shuert <coded@clicks.codes>
This is a starting point for Rust solutions to the "Build Your Own HTTP server" Challenge.
HTTP is the protocol that powers the web. In this challenge, you'll build a HTTP/1.1 server that is capable of serving multiple clients.
Along the way you'll learn about TCP servers, HTTP request syntax, and more.
Note: If you're viewing this repo on GitHub, head over to codecrafters.io to try the challenge.
The entry point for your HTTP server implementation is in src/main.rs
. Study and uncomment the relevant code, and push your changes to pass the first stage:
git add . git commit -m "pass 1st stage" # any msg git push origin master
Time to move on to the next stage!
Note: This section is for stages 2 and beyond.
cargo (1.70)
installed locally./your_server.sh
to run your program, which is implemented in src/main.rs
. This command compiles your Rust project, so it might be slow the first time you run it. Subsequent runs will be fast.git push origin master
to submit your solution to CodeCrafters. Test output will be streamed to your terminal.