mrjvs / 42-webserv Goto Github PK

sends files to cgi server

Generator for the http client requests

Signal handling for proper cleanup

title

@mrjvs:

• unbalanced brackets
• cgi index files

@pmerku:

• OPTIONS for * request
• cleanup HTTPResponder (with @mrjvs )

@piramidebouwer:

• cgi free args
• cgi close issues
• correct root directory (for cgi)

options

js: https://duktape.org/
lua: https://lucasklassmann.com/blog/2019-02-02-how-to-embeddeding-lua-in-c/

• php
• cgi
• uploading/deleting
• bonus
• proxy
• config parsing
• authentication
• allowed languages
• basic

Not all validators have been made, check todos in code

For generating requests of the server (for proxy)

currently resizes on every packet, and its slow.

plugins needed

• embedded language @mrjvs
• brainfuck runner @mrjvs
• replace in text @pmerku
• randomized 404 page (random image + randomized text) @pmerku
• json stat api @piramidebouwer

webserver that serves hello world

Currently, clients cant timeout. that needs to be fixed

yay

Add LINE, FILE and maybe func to the logger

If http:// is not provided in front of the proxy url, the server will crash

regex parser

Regex parser(const std::string &regex);
bool doesMatch = parser.match(const std::string &str);

to comply with eval sheet

Terminal commands are being parsed but not actually handled correctly
Loading and unloading of plugins should be the main feature

Comma at the end of enumerator list in LogItem.hpp is a pedantic error.
Binary color constants in LogItem.hpp are c++14 / gcc extension

For compilation errors add the pedantic flag in CMakeLists.txt:

set(CMAKE_CXX_FLAGS "-O3 -Wall -Wextra -Werror")

change to:

set(CMAKE_CXX_FLAGS "-O3 -Wall -Wextra -Werror -pedantic-errors")

every read/write operation gets added to a task queue.
task queue will do a single read/write operation.

Fails with dial tcp 127.0.0.1:8081: i/o timeout

RFC 7231 specifies responses on specific methods.
for example:

• GET -> give resources
• PUT -> create/modify resource (see #45)
• POST -> send data to resource
• HEAD -> give resource, but only header part
• OPTIONS -> give resource, but only header & allow header.
• TRACE -> trace loopback

config syntax: (may or may not be stolen from nginx)

{
  KEY value1 value2;
  KEYWORD {

  }
}

workaround: log into file and run tail -f on it

tcp can have priority packets. they need to be handled accordingly

A builder that will make the environmental variables for CGI