Info wrote:
Now I would like to limit the number of connections to one, that means only one user can connect to the web server (and can make changes on the configuration of the embedded system).
That's not a good idea. It's just not the way HTTP and browsers work. Every browser will open multiple connections and expect them to succeed. It won't use the first (successful) connection to load files that fail to download on a 2nd connection.
You should instead implement a login/logout/timeout procedure to limit configuration changes. However, that's not provided as a service by our webserver (yet?).
Simon _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
