3.2.5.1 Non-Exclusive Get Requests
A client that uses a state server makes either an exclusive or a non-exclusive request to a state server implementation for session state data.<11>
For a non-exclusive request, the client sends an HTTP request by using the message format that is specified in section 2.2.5.1.
If the server responds with a response-ok message, as specified in section 2.2.5.2, the client MUST perform implementation-specific initialization tasks if the server returns an action-flags value of "1". However, because this is a non-exclusive get request, a client MUST NOT attempt to send session state updates back to a state server. As a result, any side effects from initialization tasks that change session state information MUST not be sent back to the state server.
If the server responds with a response-locked message, as specified in section 2.2.5.2, the client MAY retain the lock-cookie, lock-age, and lock-date values for use with custom concurrency handling.<12>
If the server responds with either a response-bad-request or a response-not-found message, as specified in section 2.2.5.2, the client MAY surface some type of error back to the client's caller.<13>