| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
client
is using tls by looking at the first byte on the connection. This allows
both https and http services to be on the same port
(This used to be commit 6369dfb6585ce4d4e3028c557395f2d73c290c92)
|
|
clients using the web server.
This allows for things like
application['state'] = "shuttting down"
and then every web client can see that the server is going down
- added support for session[] data. This allows web pages to store
long term data specific to this client. It relies on
cookies. Sessions auto timeout (default timeout 5 minutes). The
timeout can be set in the scripts.
- changed from processing all .html files as esp, to only processing
.esp files as esp. This makes it easier to compare the samba web
server to appWeb as a reference implementation.
- expanded the number of standard variables setup by esp. See the
showvars.esp example page for all variables.
(This used to be commit c418b23c2ea383da8fad21b62213ec01fd135ebb)
|
|
(This used to be commit 31543e1eae03d22343ea8c970494af36eb07b41f)
|
|
This includes an embedded server side scripting system called 'esp'
(see http://www.appwebserver.org/products/esp/esp.html) and javascript
based scripting language called 'esj' (see
http://www.appwebserver.org/products/ejs/ejs.html)
The justification for including this scripting language is that it
should make it much easier to write a high quality web interface for
Samba4. The scripting language can call into any Samba4 library code
(so for example it will be able to make ldb and loadparm calls), plus
it provides easy support for forms, cookies, sessions etc.
There is still quite a bit more work to do on the web server, but
there is enough here now for people to look at and comment. I will be
committing some sample web pages that test esp functionality shortly.
(This used to be commit 26f0ba92c0c565ac9e4cb5a079d795d4262497dd)
|
