2. Coming soon: EsiGate 5.0
• Url rewriting refactored and documented
• EsiGate 5.0 is ready to be released in a few days unless a major bug is found in
5.0-beta-3
3. EsiGate extension by CGI
• This extension can be used to revamp an existing webapp without any
modification (no need to insert <esi> tags)
• In esigate.properties file you have to define the template to use, the name of the
<esi:fragment> to replace in the template and the xpath expression to keep from
tha page
• Currently it is used with a Liferay page as the template but it can be used with
anything
• CGI proposes to contribute this extension. It could be added in Github under
Esigate organisation
6. HTTP/2.0
HTTP/1.1
• connection pool+keep-alive
• blocking or non-blocking IO
HTTP/2.0
• multiplexed request thru 1 connection (no more connection pool)
• non-blocking IO only
• header compression/session-wide dictionary
Benefits:
• no more thread or connection pools
• no need to open new connections (latency)
• no more TCP slow start
• headers compression
Issues:
• sensitive to the network (initcwnd, packet loss, packet ordering)
• ALPN TLS extension not standardized in the JDK
7. • CAS and Spring-security:
– still some issues to be investigated
– Driver class should be immutable but in the current implementation,
it has to be mutable in order to alter HttpClient behaviour in case of
a redirect -> this has to be refactored
• CAS and Single Sign Out:
– CAS proxy mode does not support Single Sign Out
– https://github.com/Jasig/cas/issues/519
– Proxy tickets have to be kept in the session
• Find a name for CGI extension:
– Ideas will be appreciated
Q/A ...