Fixed bug in handling of sessions - some non-standard web apps (forwarding domains for example) in fact will have null sessions attached to their connections. Non-breaking change.
This commit is contained in:
@@ -165,7 +165,7 @@ public void createSecureSession(ISession session);
|
||||
* Processes a request from the client associated with the session. The result is placed in the response object.
|
||||
* @param request The request metadata.
|
||||
* @param response The response metadata.
|
||||
* @param session The session context for the request (never null). This is *NOT* the Session Data or Secure Session Data that the application provides, but they are accessable from this session. Provide internal (to the web server) session related data.
|
||||
* @param session The session context for the request. May be null in the case of a non-standard web app such as a forwarding domain. This is *NOT* the Session Data or Secure Session Data that the application provides, but they are accessable from this session. Provide internal (to the web server) session related data.
|
||||
* @param isSecure Whether the request was made over a secure connection and provided the correct secure id.
|
||||
* @param clientHadBadSession Whether the client's request contained a session reference that could not be found on the server.
|
||||
* @param connectionContext The context object for the connection (socket) between the client (web browser) and server (web server).
|
||||
|
||||
Reference in New Issue
Block a user