3 February 2018, 10:25
i have been playing around with named pipes on Linux a bit and wanted to see how hiawatha treats them.
So, if i create a named pipe in a directory served by hiawatha and send a request for that "file" one of two things happen:
if the fifo has already a pending write operation, hiawatha just returns a blank page, regardless of what is send through the fifo.
If there is no open write handle, hiawatha just waits. In theory, this could be used by clients to flood the server with open file handles but due to hiawathas excellent security features, this is not any threat.
However, in my opinion the way how hiawatha deals with fifos is not optimal. It should either ignore/forbid them completely (apache e.g. sends a 403 for "non regular files"), or implement them in a meaningful way.
What do you think?
This topic has been closed.