RanniSch webserv issues

RanniSch / webserv

0 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

with canons on spatzen

#95 MaxIhme closed 1 year ago
0
compiles again and runs again

#94 MaxIhme closed 1 year ago
0
compiles again

#93 MaxIhme closed 1 year ago
0
Occf

#92 MaxIhme closed 1 year ago
0
Memory

#91 MaxIhme closed 1 year ago
0
some memory cleaned in config

#90 MaxIhme closed 1 year ago
0
config checks location to have / at beginning but not at end

#89 MaxIhme closed 1 year ago
0
fixed return and adress that is missing an / at the end

#88 MaxIhme closed 1 year ago
0
[NOT IMPONTANT ONLY FOR ME] • There should be only one read or one write per client per select() (or equivalent). Ask the group to show you the code from the select() (or equivalent) to the read and write of a client.

#87 LukasKava closed 1 year ago
0
[MY NOT IMPORTANT] The select() (or equivalent) should be in the main loop and should check file descriptors for read and write AT THE SAME TIME. If not, the grade is 0 and the evaluation process ends now.

#86 LukasKava closed 1 year ago
0
• Ask if they use only one select() (or equivalent) and how they've managed the server to accept and the client to read/write.

#85 LukasKava closed 1 year ago
0
Ask what function the group used for I/O Multiplexing.

#84 LukasKava closed 1 year ago
0
Siege & stress test: Check if there is no hanging connection.

#83 RanniSch closed 1 year ago
1
Siege & stress test: Verify there is no memory leak (Monitor the process memory usage. It should not go up indefinitely).

#82 RanniSch closed 1 year ago
2
Fixed seg faults and timeout

#81 LukasKava closed 1 year ago
0
empty spaces can be used for get

#80 MaxIhme closed 1 year ago
0
Restrict download size

#79 MaxIhme closed 1 year ago
0
Download 3,9GB Data from the server

#78 MaxIhme closed 1 year ago
0
test root test return

#77 MaxIhme opened 1 year ago
0
new_updates

#76 LukasKava closed 1 year ago
0
bug fix ResponseMessage gets an empty string to createResponse() -> n…

#75 MaxIhme closed 1 year ago
0
Configuration: • Limit the client body (use: curl -X POST -H "Content-Type: plain/text" --data "BODY IS HERE write something shorter or longer than body limit").

#74 MaxIhme closed 1 year ago
2
Port Issues: Launch multiple servers at the same time with different configurations but with common ports. Does it work? If it does, ask why the server should work if one of the configurations isn't functional. Keep going.

#73 MaxIhme opened 1 year ago
3
Configuration: Setup multiple servers with different hostnames (use something like: curl --resolve example.com:80:127.0.0.1 http://example.com/ (http://example.com/))

#72 MaxIhme closed 1 year ago
5
Configuration: Setup multiple servers with different ports.

#71 MaxIhme closed 1 year ago
5
Siege & stress test: You should be able to use siege indefinitely without having to restart the server (take a look at siege -b).

#70 RanniSch closed 1 year ago
4
Siege & stress test: Availability should be above 99.5% for a simple GET on an empty page with a siege -b on that page.

#69 RanniSch closed 1 year ago
4
PROBLEM: Siege & stress test: Use Siege to run some stress tests.

#68 RanniSch closed 1 year ago
3
PROBLEM: Mandatory Part: Check the code and ask questions: Launch the installation of siege with homebrew.

#67 RanniSch closed 1 year ago
1
PROBLEM: Guidelines: You must also verify the absence of memory leaks. Any memory allocated on the heap must be properly freed before the end of execution. You are allowed to use any of the different tools available on the computer, such as leaks, valgrind, or e_fence. In case of memory leaks, tick the appropriate flag.

#66 RanniSch closed 1 year ago
3
Port issues: In the configuration, try to setup the same port multiple times. It should not work.

#65 RanniSch closed 1 year ago
3
PROBLEM: Port issues: In the configuration file setup multiple ports and use different websites. Use the browser to ensure that the configuration works as expected and shows the right website.

#64 RanniSch closed 1 year ago
4
PROBLEM Check with a browser: Try anything you want to.

#63 RanniSch closed 1 year ago
3
Check with a browser: Look at the request header and response header.

#62 RanniSch closed 1 year ago
4
PROBLEM Check with a browser: It should be compatible to serve a fully static website.

#61 RanniSch closed 1 year ago
4
PROBLEM: Basic checks: Using telnet, curl, prepared files, demonstrate that the following features work properly: For every test you should receive the appropriate status code.

#60 RanniSch closed 1 year ago
3
PROBLEM: Basic checks: Using telnet, curl, prepared files, demonstrate that the following features work properly: GET, POST and DELETE requests should work.

#59 RanniSch closed 1 year ago
2
PROBLEM: Basic checks: Using telnet, curl, prepared files, demonstrate that the following features work properly: Upload some file to the server and get it back.

#58 RanniSch closed 1 year ago
2
check return from different sides

#57 MaxIhme closed 1 year ago
1
check with wrong cgi path in config

#56 MaxIhme closed 1 year ago
1
check for allowed methods in conf when there is put or so

#55 MaxIhme opened 1 year ago
0
Time

#54 LukasKava closed 1 year ago
0
Try other method opening cgi

#53 MaxIhme opened 1 year ago
0
Check with a browser: Try to list a directory.

#52 RanniSch opened 1 year ago
2
Check with a browser: Try a redirected URL.

#51 RanniSch closed 1 year ago
8
Check CGI: You need to test with files containing errors to see if the error handling works properly. You can use a script containing an infinite loop or an error; you are free to do whatever tests you want within the limits of acceptability that remain at your discretion. The group being evaluated should help you with this. The server should never crash and an error should be visible in case of a problem.

#50 RanniSch opened 1 year ago
3
Mandatory Part: The project must compile without any re-link issue. If not, use the 'Invalid compilation' flag.

#49 RanniSch opened 1 year ago
2
Check with a browser: Try a wrong URL on the server.

#48 RanniSch opened 1 year ago
2
Check with a browser: Use the reference browser of the team. Open the network part of it, and try to connect to the server using it.

#47 RanniSch closed 1 year ago
3
Check CGI: With the help of the students you should check that everything is working properly. You have to test the CGI with the "GET" and "POST" methods.

#46 RanniSch closed 1 year ago
3