Hi,
It has been observed that Sensitive information within URLs is getting logged 
in various locations, including the user's browser, the web server, and any 
forward or reverse proxy servers between the two endpoints. URLs may also be 
displayed on-screen, bookmarked or emailed around by users. They may be 
disclosed to third parties via the Referer header when any off-site links are 
followed. Placing session tokens into the URL increases the risk that they will 
be captured by an attacker.
Is there any alternative mechanism for transmitting session tokens, such as 
HTTP cookies or hidden fields in forms that are submitted using the POST method.

Regards
Madhukar Bhosale

Reply via email to