+ in fill_script_path() : scipt_path and script_info are filled, removing leadin dot

+ in _cgi_pos() : check validity of extension if it's only alpha characters
+ severall pbm appears

README.md

@@ -2,17 +2,21 @@
 ## work together
 
 #### next commit
-+ fixed pbm in extract_line : delete the line and the newline sequence character
-+ fixed pbm n _cgi_pos : last return is npos, not pos
++ in fill_script_path() : scipt_path and script_info are filled, removing leadin dot
++ in _cgi_pos() : check validity of extension if it's only alpha characters
++ severall pbm appears
 
 #### TODO hugo
-- `_is_cgi()` and `_fill_cgi_path()`
-- two cgi tests :
-?	- a basic form with "name" and "something", that return a html page with that
-?		- for GET and POST
-?	- a script called by a file extension in URI
+- pbm : `http://localhost:4040/cgi-bin/cgi.sh`
 
 #### questions
+- does the root always start with leading "." ?
+- how should we handle a wrong url like `http://localhost/cgi-bin/wrong.phpp/good.php` ?
+	- do we serve `./srcs/cgi-bin/good.php` ?
+	- or do we return 404 "not found" ?
+	- for now, execve would crash, but that doesn't produce a 404 error, rather a 500, is it bad ?
+- if a url has a file with extension, but it's not a cgi extension, is it necessary to look further ?
+	- ex. `http://localhost/file.php/file.py` for `cgi_ext py;` ?
 - the response page is received long after the cgi-script is done, why ?
 
 ---