Updates 48000 » History » Version 3
Version 2 (Pierre Marc, 02/20/2012 11:52 AM) → Version 3/9 (Pierre Marc, 07/26/2013 04:55 PM)
h1. 4.7.009 4.8.000 Updates
h2. Bugs
* In case of crash the log table may be corrupted so it becomes impossible to analyze the crash in the logs. We know rebuild the log table from the disk if this one is corrupted in memory.
h2. New features
* Management of the HTTP X-Forwarded-For header. This parameter allows Nirva to retrieve the sender IP address in case there is a proxy or a load balancer in the route. This is a security enhancement.
* One can define a trigger for external commands in application. This is a procedure (or several procedures) called before executing a command coming from a client (browser, xml, c++, java, etc...). The external trigger procedure name is set in the application.dsc file for deployment.
* Adding a chapter in the documentation about applications.
h2. Bugs
* In case of crash the log table may be corrupted so it becomes impossible to analyze the crash in the logs. We know rebuild the log table from the disk if this one is corrupted in memory.
h2. New features
* Management of the HTTP X-Forwarded-For header. This parameter allows Nirva to retrieve the sender IP address in case there is a proxy or a load balancer in the route. This is a security enhancement.
* One can define a trigger for external commands in application. This is a procedure (or several procedures) called before executing a command coming from a client (browser, xml, c++, java, etc...). The external trigger procedure name is set in the application.dsc file for deployment.
* Adding a chapter in the documentation about applications.