Correcting the problem with path not ended with '/'

In the previous release, path not ended with '/' would be treated as one ended with '/'. This would make the relative paths in HTML tag be treated in a wrong way. For example, if a client request the path "/www2" and ESP8266WebServer found there's a index.html in "/www2" folder, it would returning the index.html file back to the client. In the mean time, the client thinks the path is "/", not "/www2/", so if there's a relative path such as "main.css" in the HTML, the client would request "/main.css" but not "/www2/main.css". In this version, the same request path "/www2" would be response as "400 Bad request".

A veriosn with correct http redirect response header.

A version that can use external css file and so on.I use the http redirect response header to tell client the real path of the default index(.p).html file instead of returning the content the default html file directly.By doing this, clients such as browsers can get resources via relative links correctly.

v0.1.0

A version that can be used for IoT devices.