The browser is the one who will attempt new connections on img tags, and on attempting those connections, they will most likely fail. Have in mind that this server, as simple as it is, can not server more than one connection at a time: if it's serving the main page, it cannot accept more connections to serve the images, for example, they will simply fail until the last client disconnects. To be able to accept multiple connections at the same time, you will have to deliver the management of the client socket to someone else (usually a thread), and allow the server socket to be ready to accept new connections right away, which will be again, passed on to another thread. This is just how real servers work. This example shows you the basics on managing a single connection, now you will need to work on this to meet your multiple connection needs. Regards.

Eduardo Piombino I tested and worked! I was using a wrong value for the image: I used href inside <a tag instead of src= . Using src="" the browser started new connections to get the image automatically. Thank you.

Well I'm glad it did. Do you know what really happened behind curtains?

Eduardo Piombino that TCP Server component is feasible for a HTTP webserver. Might even be suitable for SSL. My error was to write an html page with <img href="pic.jpg"/> instead of <img src="pic.jpg"/>. When I did src="" the browser made another connection into the TCPServer's port that made possible to handle resources and HTML.

$_POST['name']