Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I make a HTTPS request to
subdomain.example.com/api/login?mytoken=JLK90GFSSFGDS4GFRW0
along with uploading a cookie, can a packet sniffer know:
In general, what information is encrypted and what is left plain for a HTTPS packet?
Everything apart from the hostname is encrypted – so in your example the domain name and subdomain are in clear text, everything else is encrypted.
See Does SSL also encrypt cookies? for more details.
[edited: initial version mistakenly stated that the entire URL was in cleartext. http://en.wikipedia.org/wiki/Transport_Layer_Security makes it quite clear that the server and client first negotiate their encryption, then the application-layer HTTP packets (with the full URL) is sent over this encrypted link.]