HTTP Session: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 20: | Line 20: | ||
* [[HTTP Session Passivation]] | * [[HTTP Session Passivation]] | ||
* [[JBossWeb/Tomcat HTTP Session Implementation Details]] | * [[JBossWeb/Tomcat HTTP Session Implementation Details]] | ||
* [[JBoss HTTP Session Troubleshooting]] | |||
* [[Curl#Simulation_of_a_HTTP_Session_JSessionID|Simulation of a HTTP Session with curl]] | * [[Curl#Simulation_of_a_HTTP_Session_JSessionID|Simulation of a HTTP Session with curl]] | ||
=Example= | =Example= | ||
{{Internal|Session Servlet Example|Session Servlet Example}} | |||
Latest revision as of 20:37, 7 February 2018
External
- How can I disable session creation for RESTEasy application? https://access.redhat.com/solutions/1290373
Internal
Overview
HTTP is a stateless protocol and maintaining a conversational state of the server is not directly supported by the protocol. HTTP provides no build-in way for a server to recognize that a sequence of requests originate from the same user. Since CGI, developers have been using various techinques to track the session: user authentication, hidden form fields, URL rewriting and persistent cookies. The servlet API brings improved support for session tracking. The support is built in top of the traditional techniques and it simplifies the task of session tracking in your servlets.
Subjects
- Methods to Maintain a HTTP Session
- Servlet Session Tracking API
- HTTP Session Timeout
- HTTP Session Replication
- HTTP Session Passivation
- JBossWeb/Tomcat HTTP Session Implementation Details
- JBoss HTTP Session Troubleshooting
- Simulation of a HTTP Session with curl