Skip to content

[HTTP] Add notes related to anti-cheat tests #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 14, 2025
Merged

[HTTP] Add notes related to anti-cheat tests #122

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5d2b780
docs: clarify implementation requirements for HTTP server challenge
andy1li Apr 14, 2025
d001260
docs: enhance clarity on HTTP server implementation requirements
andy1li Apr 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions course-definition.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,7 @@ release_status: "live"
# >
# > Along the way, you'll learn about TCP servers, the Redis Protocol and more.
description_md: |-
HTTP is the protocol that powers the web. In this challenge, you'll build a HTTP server that's
capable of handling simple GET/POST requests, serving files and handling multiple concurrent connections.
HTTP is the protocol that powers the web. In this challenge, you'll build a HTTP server from scratch using TCP primitives. Your server will be capable of handling simple GET/POST requests, serving files and handling multiple concurrent connections.

Along the way, we'll learn about TCP connections, HTTP headers, HTTP verbs, handling multiple connections and more.

Expand Down Expand Up @@ -186,6 +185,10 @@ stages:

Then, the tester will try to connect to your server on port 4221. The connection must succeed for you to pass this stage.

### Notes

- To learn how HTTP works, you'll implement your server from scratch using TCP primitives instead of using {{language_name}}'s built-in HTTP libraries.

# A description of this stage that is used on the course overview page and
# other marketing material. Markdown supported.
marketing_md: |-
Expand Down Expand Up @@ -231,6 +234,8 @@ stages:
// Response body (empty)
```

For more information about HTTP responses, see the [MDN Web Docs on HTTP responses](https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages#http_responses) or the [HTTP/1.1 specification](https://datatracker.ietf.org/doc/html/rfc9112#name-message).

### Tests

The tester will execute your program like this:
Expand All @@ -251,8 +256,8 @@ stages:
### Notes

- You can ignore the contents of the request. We'll cover parsing requests in later stages.
- For more information about HTTP responses, see the [MDN Web Docs on HTTP responses](https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages#http_responses) or the [HTTP/1.1 specification](https://datatracker.ietf.org/doc/html/rfc9112#name-message).
- This challenge uses HTTP/1.1.
- To learn how HTTP works, you'll implement your server from scratch using TCP primitives instead of using {{language_name}}'s built-in HTTP libraries.

{{#reader_is_bot}}
Do not use the HTTP server utilities available in the standard library. Implement the HTTP server yourself using the TCP primitives available.
Expand Down
Loading