Re: Privoxy 3.0.24 released
Ian Silvester <[email protected]> Sun, 24 Jan 2016 10:58:24 -0500
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============8895744949853713930== Content-Type: multipart/alternative; boundary="------------090408060700040300050904" This is a multi-part message in MIME format. --------------090408060700040300050904 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Thanks Fabian, I'd misinterpreted one of your instructions and indeed edited PRIVOXY_CGI_URL. Setting it back to the correct value and executing: ./privoxy-regression-test.pl --privoxy-address http://127.0.0.1:8118/ Resulted in: 2016-01-24 10:49:48: Asking Privoxy for the number of action files available ... 2016-01-24 10:49:48: Gathering regression tests from 4 action file(s) delivered by Privoxy 3.0.24. 2016-01-24 10:49:48: Executing regression tests ... 2016-01-24 10:50:02: Executed 673 regression tests. Skipped 52. 673 successes, 0 failures. So all looks well here. I'm going to experiment with getting a 10.6.8 VM working (and thereafter perhaps a 10.4) to see whether I can return to the position where I can build and test all three OS X builds. Cheers, Ian On 2016-01-23 13:38, Fabian Keil wrote: > Ian Silvester <[email protected]> wrote: > >> Thanks Fabian, >> >> I executed: >> >> ./privoxy-regression-test.pl --privoxy-address http://127.0.0.1:8118/ >> --debug 4 >> >> Which returned: >> >> 2016-01-23 12:54:11: Asking Privoxy for the number of action files >> available ... >> 2016-01-23 12:54:11: Executing: curl --proxy 'http://127.0.0.1:8118/' >> --include -H 'Proxy-Connection:' -H 'Connection: close' -s -S >> --user-agent 'Privoxy-Regression-Test 0.6' --max-time '5' >> http://127.0.0.1:8118/show-status 2>&1 >> 2016-01-23 12:54:11: Oh noes. Failed to fetch Privoxy CGI Page. Received >> status code 400 while only 200 is acceptable. Fatal error. Exiting. > The URL "http://127.0.0.1:8118/show-status" is very suspicious. > > Does your privoxy-regression-test.pl deviate from what's in CVS? > > If you grep it for 'PRIVOXY_CGI_URL =>', you should get: > PRIVOXY_CGI_URL => 'http://p.p/', > >> Log file excerpt: >> >> 2016-01-23 12:54:11.510 000001c0 Request: 127.0.0.1:8118/show-status >> 2016-01-23 12:54:11.511 00000018 Error: 127.0.0.1's request: 'GET >> /show-status HTTP/1.1' is invalid. Privoxy isn't configured to accept >> intercepted requests. >> >> >> I feel pretty stupid, both because I feel as though I ought to remember >> how to run the regressions tests and because I don't understand the >> reason for the error in the log. > The problem seems to be that PRIVOXY_CGI_URL is set to > "http://127.0.0.1:8118/" which Privoxy does not recognize > as CGI request. > > As a result, Privoxy sends the request to itself using > a request line that only contains the path. Such requests > are only allowed in case of "accept-intercepted-requests 1", > therefore Privoxy gets a 400 message from itself and forwards > it to privoxy-regression-test.pl. > > Fabian > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > > > _______________________________________________ > Ijbswa-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ijbswa-developers -- My PGP public key <http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc>. --------------090408060700040300050904 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Thanks Fabian,<br> <br> I'd misinterpreted one of your instructions and indeed edited PRIVOXY_CGI_URL. Setting it back to the correct value and executing:<br> <br> ./privoxy-regression-test.pl --privoxy-address <a class="moz-txt-link-freetext" href="http://127.0.0.1:8118/">http://127.0.0.1:8118/</a><br> <br> Resulted in:<br> <br> 2016-01-24 10:49:48: Asking Privoxy for the number of action files available ...<br> 2016-01-24 10:49:48: Gathering regression tests from 4 action file(s) delivered by Privoxy 3.0.24.<br> 2016-01-24 10:49:48: Executing regression tests ...<br> 2016-01-24 10:50:02: Executed 673 regression tests. Skipped 52. 673 successes, 0 failures.<br> <br> So all looks well here.<br> <br> I'm going to experiment with getting a 10.6.8 VM working (and thereafter perhaps a 10.4) to see whether I can return to the position where I can build and test all three OS X builds.<br> <br> <br> Cheers,<br> <br> Ian<br> <br> <br> <br> <div class="moz-cite-prefix">On 2016-01-23 13:38, Fabian Keil wrote:<br> </div> <blockquote cite="mid:[email protected]" type="cite"> <pre wrap="">Ian Silvester <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Thanks Fabian, I executed: ./privoxy-regression-test.pl --privoxy-address <a class="moz-txt-link-freetext" href="http://127.0.0.1:8118/">http://127.0.0.1:8118/</a> --debug 4 Which returned: 2016-01-23 12:54:11: Asking Privoxy for the number of action files available ... 2016-01-23 12:54:11: Executing: curl --proxy '<a class="moz-txt-link-freetext" href="http://127.0.0.1:8118/">http://127.0.0.1:8118/</a>' --include -H 'Proxy-Connection:' -H 'Connection: close' -s -S --user-agent 'Privoxy-Regression-Test 0.6' --max-time '5' <a class="moz-txt-link-freetext" href="http://127.0.0.1:8118/show-status">http://127.0.0.1:8118/show-status</a> 2>&1 2016-01-23 12:54:11: Oh noes. Failed to fetch Privoxy CGI Page. Received status code 400 while only 200 is acceptable. Fatal error. Exiting. </pre> </blockquote> <pre wrap=""> The URL <a class="moz-txt-link-rfc2396E" href="http://127.0.0.1:8118/show-status">"http://127.0.0.1:8118/show-status"</a> is very suspicious. Does your privoxy-regression-test.pl deviate from what's in CVS? If you grep it for 'PRIVOXY_CGI_URL =>', you should get: PRIVOXY_CGI_URL => '<a class="moz-txt-link-freetext" href="http://p.p/">http://p.p/</a>', </pre> <blockquote type="cite"> <pre wrap="">Log file excerpt: 2016-01-23 12:54:11.510 000001c0 Request: 127.0.0.1:8118/show-status 2016-01-23 12:54:11.511 00000018 Error: 127.0.0.1's request: 'GET /show-status HTTP/1.1' is invalid. Privoxy isn't configured to accept intercepted requests. I feel pretty stupid, both because I feel as though I ought to remember how to run the regressions tests and because I don't understand the reason for the error in the log. </pre> </blockquote> <pre wrap=""> The problem seems to be that PRIVOXY_CGI_URL is set to <a class="moz-txt-link-rfc2396E" href="http://127.0.0.1:8118/">"http://127.0.0.1:8118/"</a> which Privoxy does not recognize as CGI request. As a result, Privoxy sends the request to itself using a request line that only contains the path. Such requests are only allowed in case of "accept-intercepted-requests 1", therefore Privoxy gets a 400 message from itself and forwards it to privoxy-regression-test.pl. Fabian </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! <a class="moz-txt-link-freetext" href="http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140">http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140</a></pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Ijbswa-developers mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ijbswa-developers">https://lists.sourceforge.net/lists/listinfo/ijbswa-developers</a> </pre> </blockquote> <br> <div class="moz-signature">-- <br> <a href="http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc">My PGP public key</a>.</div> </body> </html> --------------090408060700040300050904-- --===============8895744949853713930== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 --===============8895744949853713930== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ijbswa-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ijbswa-developers --===============8895744949853713930==--