Re: Compilation warnings in jbsockets.c
Ian Silvester <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2013-03-06, at 3:29 PM, Fabian Keil wrote: > Ian Silvester <[email protected]> wrote: > >> On 2013-03-06, at 8:17 AM, Fabian Keil wrote: > >>> In this case you could verify that http://p.p/ still shows the >>> same "This is Privoxy ..." message >> >> It does. >> >>> and that the regression tests still pass. >> >> For some reason curl cannot resolve p.p/ (and hence privoxy-regression-test.pl >> fails) though the browsers can. The last time I ran the regression tests I didn't >> run into this issue and my network and Privoxy configuration is unchanged apart >> from going to 3.0.21's code which I sincerely doubt is the cause. It's not down >> to you to fix my configuration but do you have any pointers? > > The fact that curl even tries to resolve p.p indicates > that it isn't using Privoxy as proxy. > > If the environment variable http_proxy isn't set you'll > have to either set it or use the --privoxy-address option. > > If I remember correctly, you mentioned using it in the past. Ach, sorry, you're absolutely right. Should have checked email archives before posting. Regression went well, only one failure and that didn't relate to the code change hence I'll commit it. The failure is something you might be interested in though Fabian since it has arisen since 3.0.20. My default OS X config now serves the user manual locally, and test 591 fails as follows: ./privoxy-regression-test.pl --privoxy-address 127.0.0.1:8118 --show-skipped-tests --max-level 109 2013-03-06 15:49:05: Asking Privoxy for the number of action files available ... 2013-03-06 15:49:05: Gathering regression tests from 4 action file(s) delivered by Privoxy 3.0.21. 2013-03-06 15:49:05: Executing regression tests ... 2013-03-06 15:49:11: Skipping test 355: Ignore flag is set. 2013-03-06 15:49:11: Skipping test 356: Ignore flag is set. 2013-03-06 15:49:11: Skipping test 357: Ignore flag is set. 2013-03-06 15:49:11: Skipping test 358: Ignore flag is set. 2013-03-06 15:49:11: Skipping test 359: Ignore flag is set. 2013-03-06 15:49:12: Skipping test 482: depends on 'FEATURE_CONNECTION_KEEP_ALIVE' being set to 'No'. 2013-03-06 15:49:12: Skipping test 483: depends on 'FEATURE_CONNECTION_KEEP_ALIVE' being set to 'No'. 2013-03-06 15:49:12: Skipping test 484: depends on config line matching: 'connection-sharing\s+0'. 2013-03-06 15:49:12: Skipping test 485: depends on config line matching: 'connection-sharing\s+1'. 2013-03-06 15:49:12: Skipping test 486: depends on config line matching: 'connection-sharing\s+1'. 2013-03-06 15:49:12: Skipping test 490: depends on 'FEATURE_CONNECTION_KEEP_ALIVE' being set to 'No'. 2013-03-06 15:49:12: Skipping test 499: depends on 'FEATURE_GRACEFUL_TERMINATION' being set to 'Yes'. 2013-03-06 15:49:13: Skipping test 524: depends on 'FEATURE_TOGGLE' being set to 'No'. 2013-03-06 15:49:14: Ooops. We expected status code 200, but received: 500. 2013-03-06 15:49:14: Failure for test 591. URL 'http://p.p/user-manual/p_doc.css' and expected status code '200' 2013-03-06 15:49:15: Executed 667 regression tests. Skipped 13. 666 successes, 1 failures. My config is as follows: user-manual /usr/local/share/doc/privoxy/user-manual/ p_doc.css is in the base folder for documentation (/usr/local/share/doc/privoxy), not in the user-manual subfolder. Is this related to the documentation cleanup you've done since 3.0.20 or something at my end? Ian > > Fabian > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev_______________________________________________ > Ijbswa-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ijbswa-developers ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev