Kiran, On Thu, Feb 14, 2013 at 03:09:35AM +0000, Mahajan, Kiran wrote: > I figured it out from the Polipo logs. > curl_easy_setopt(curl_handle, CURLOPT_HTTPPROXYTUNNEL, 1); > curl_easy_setopt(curl_handle, CURLOPT_PROXY, "127.0.0.1:8123"); > > But the http:// is not present in the response from the web server which is > before the libcurl where Polipo gets it cache the object and then forward it > to the libcurl/webkit.
I'm not sure I understand what you mean. In any case, you should really figure where exactly the "http://"; prefix disappears. For instance, assuming tcpdump is available on your system, you could use the following commands to dump polipo/browser and polipo/web traffic: tcpdump -s 65535 -w browser-polipo.dump port 8123 tcpdump -s 65535 -w polipo-web.dump port 80 Then open the files with wireshark to isolate the faulty requests. If you find out that polipo receives paquets containing "http://"; but drops it internally, or fails to cache it in some other way, then please report the bug here. Best, -- Gabriel ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
