To me this does not look like an esp-idf bug. I ran into the same problem on both getpeername and getsockname. It seems the esp_http_server always starts its listener using IPV6 (which is hardcoded in esp-idf), so you cannot use the IPV4 macros on the getpeername/getsockname calls. So struct sockadd...

Im looking to see if it is possible to use the new esp_http_server. The usecase is to serve files from spiffs, so you can start creating a website. Current architecture of this server requires me to register a handler for every URI. I might be overlooking something here, Is there any way to do this ...