<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Session hijacking - Page 5 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=session_hijacking&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=session_hijacking&amp;p=6">3.Next</a>
</p>
<p>session hijacking, but they were difficult to exploit due to the vagaries of most early HTTP 1.0 servers and browsers. As HTTP 1.0 has been designated as a fallback for HTTP 1.1 since the early 2000s--and as HTTP 1.0 servers are all essentially HTTP 1.1 servers the session hijacking problem has evolved into a nearly permanent security risk.</p>

<p>The introduction of <a href="page.php?w=HTTP_cookie">supercookies</a> and other features with the modernized HTTP 1.1 has allowed for the hijacking problem to become an ongoing security problem. Webserver</p><p>
<a accesskey="1" href="page.php?w=session_hijacking&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=session_hijacking&amp;p=6">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
