Раздел 10. Apache modules Пункты: 85 86 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 163 164 165 166 167 168 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 203 204 205 206 207 208 209 210 211 212 213 RU EN Пункт 192. Apache Module mod_session_dbd
SummaryWarningThe session modules make use of HTTP cookies, and as such can fall victim to Cross Site Scripting attacks, or expose potentially private information to clients. Please ensure that the relevant risks have been taken into account before enabling the session functionality on your server. This submodule of Sessions can either be anonymous, where the session is keyed by a unique UUID string stored on the browser in a cookie, or per user, where the session is keyed against the userid of the logged in user. SQL based sessions are hidden from the browser, and so offer a measure of privacy without the need for encryption. Different webservers within a server farm may choose to share a database, and so share sessions with one another. For more details on the session interface, see the documentation for
the DBD ConfigurationBefore the There are four queries required to keep a session maintained, to select an existing session, to update an existing session, to insert a new session, and to delete an expired or empty session. These queries are configured as per the example below. Sample DBD configurationDBDriver pgsql DBDParams "dbname=apachesession user=apache password=xxxxx host=localhost" DBDPrepareSQL "delete from session where key = %s" deletesession DBDPrepareSQL "update session set value = %s, expiry = %lld, key = %s where key = %s" updatesession DBDPrepareSQL "insert into session (value, expiry, key) values (%s, %lld, %s)" insertsession DBDPrepareSQL "select value from session where key = %s and (expiry = 0 or expiry > %lld)" selectsession DBDPrepareSQL "delete from session where expiry != 0 and expiry < %lld" cleansession Anonymous SessionsAnonymous sessions are keyed against a unique UUID, and stored on the browser within an HTTP cookie. This method is similar to that used by most application servers to store session information. To create a simple anonymous session and store it in a postgres database table called apachesession, and save the session ID in a cookie called session, configure the session as follows: SQL based anonymous sessionSession On SessionDBDCookieName session path=/ For more examples on how the session can be configured to be read
from and written to by a CGI application, see the
For documentation on how the session can be used to store username
and password details, see the Per User SessionsPer user sessions are keyed against the username of a successfully authenticated user. It offers the most privacy, as no external handle to the session exists outside of the authenticated realm. Per user sessions work within a correctly configured authenticated
environment, be that using basic authentication, digest authentication
or SSL client certificates. Due to the limitations of who came first,
the chicken or the egg, per user sessions cannot be used to store
authentication credentials from a module like
To create a simple per user session and store it in a postgres database table called apachesession, and with the session keyed to the userid, configure the session as follows: SQL based per user sessionSession On SessionDBDPerUser On Database HousekeepingOver the course of time, the database can be expected to start accumulating
expired sessions. At this point, the WarningThe administrator will need to set up an external process via cron to clean out expired sessions. SessionDBDCookieName Directive
The An optional list of cookie attributes can be specified, as per the example below. These attributes are inserted into the cookie as is, and are not interpreted by Apache. Ensure that your attributes are defined correctly as per the cookie specification. Cookie with attributesSession On SessionDBDCookieName session path=/private;domain=example.com;httponly;secure;version=1; SessionDBDCookieName2 Directive
The An optional list of cookie attributes can be specified, as per the example below. These attributes are inserted into the cookie as is, and are not interpreted by Apache. Ensure that your attributes are defined correctly as per the cookie specification. Cookie2 with attributesSession On SessionDBDCookieName2 session path=/private;domain=example.com;httponly;secure;version=1; SessionDBDCookieRemove Directive
The In a reverse proxy situation where the Apache server acts as a server frontend for a backend origin server, revealing the contents of the session ID cookie to the backend could be a potential privacy violation. When set to on, the session ID cookie will be removed from the incoming HTTP headers. SessionDBDDeleteLabel Directive
The SessionDBDInsertLabel Directive
The If an attempt to update the session affects no rows, this query will be called to insert the session into the database. SessionDBDPerUser Directive
The SessionDBDSelectLabel Directive
The SessionDBDUpdateLabel Directive
The If an attempt to update the session affects no rows, the insert query will be called to insert the session into the database. If the database supports InsertOrUpdate, override this query to perform the update in one query instead of two. Пункты: 85 86 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 163 164 165 166 167 168 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 203 204 205 206 207 208 209 210 211 212 213 |