Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!news-1.dfn.de!news.dfn.de!news.informatik.hu-berlin.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Peter Pearson Newsgroups: comp.lang.python Subject: Re: encrypt the http request url on the local machine Date: 9 Dec 2014 17:08:24 GMT Lines: 15 Message-ID: References: <0b8ebdd8-9df5-4a99-b226-590cd3d3cef6@googlegroups.com> X-Trace: individual.net 4b443nRLVwppHspTDTCZ1QdidwtcBLuUPxUbQnP7Pod5CNnB5l Cancel-Lock: sha1:KvFwTc/RJd6bBAQtxPSdJuViw8U= User-Agent: slrn/pre1.0.0-18 (Linux) Xref: csiph.com comp.lang.python:82233 On Mon, 8 Dec 2014 22:58:20 -0800 (PST), iMath wrote: > my software on the local machine needs to send http request to a > specific web server , is there any way to protect the http request url > from being found by Packet analyzer software like Wireshark and > fiddler. The sever is not mine, so I can do nothing in the server . This is what Tor (onion routing) is for. Vaguely speaking ('cause I don't know much about Tor), you encrypt your entire HTTP request and send it to a Tor node. It gets passed around among Tor nodes until an "exit node" decrypts it and sends it to the destination server. Be aware, though, that if the destination server doesn't do HTTPS, the conversation between it and the Tor exit node is readable by snoops. -- To email me, substitute nowhere->runbox, invalid->com.