Re: [lwip-users] Single connection with "httpd" web server

[Noam weissman]

Hi,

You mean one user, not one connection. HTTP creates multiple connections
to load a page.

I have implemented this by adding a session ID. That means that you need
to change the web server
to support that. 

In general you create a login page and after successful login you return
a session ID to the page. You need code to save this
Globally and every new request sent to the server you add that session
ID. The web server will check if the SSID is valid it will
Reply with the requested data. If not it will force the login page.

This is a brief description.

BR,
Noam.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Info
Sent: Tuesday, May 12, 2015 4:23 PM
To: address@hidden
Subject: [lwip-users] Single connection with "httpd" web server

Hi all

I'm using the "httpd" (httpd.c) web server from the lwIP contribution
package on top of the lwIP 1.4.1 . The web server is running well
without any problems. I activated the LWIP_HTTPD_SUPPORT_11_KEEPALIVE
macro to keep a connection to web server open. This also works like
excepted. 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). I think it should
be implemented in the http_accept() in such a way, that any new
connection is denied if already a connection is open.
Is this correct or how do I implement such a behaviour ? Any suggestion
would helpful.

Kind regards,
Roland


_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

 
 
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************