Re: Release date for Privoxy 3.0.20 beta

On 1/1/13, Fabian Keil <[email protected]> wrote:
> Lee <[email protected]> wrote:
>
>> On 12/31/12, Fabian Keil <[email protected]> wrote:
>> > Lee <[email protected]> wrote:
>> >
>> >> On 12/29/12, Fabian Keil <[email protected]> wrote:
>> >> > I believe there are enough changes in CVS to warrant a new release.
>> >> >
>> >> > As several of the changes are HTTP-related and affect pretty
>> >> > much every request, I think it should be a beta.
>> >> >
>> >> > I propose we release Privoxy 3.0.20 beta in the middle of
>> >> > January and 3.0.21 stable a couple of weeks later.
>
> New proposal: about 2 weeks after the Windows-specific issues are fixed.

Your latest patch fixed it, so it's still on track for middle of Jan :)

>> >> restart privoxy, restart firefox, clear the cache, go here
>> >>   http://www.microsoft.com/en-us/download/default.aspx
>> >> then click on the link for the directx download
>> >>   http://www.microsoft.com/en-us/download/details.aspx?id=35
>> >>
>> >> The 2nd page never displays
>> >>
>> >> I'll send the log + my config in a unicast
>> >
>> > Thanks.
>> >
>> > Please try the attached patch. If it doesn't help,
>>
>> browser immediately comes back with an error message about the proxy
>> closing the connection
>
> I managed to get the logic wrong in a last-minute change. It should be:
>
> +         if (!data_is_available(fd, 0))
> +         {
> +            break;
> +         }

That fixed it.  I haven't noticed any problems after hitting a lot of
different web sites except for the change adding "http://" to the
request log doesn't add "https://" for secure connections - for
example:

2013-01-01 14:35:09.641 00000464 Request:
http://www.epa.gov/radnet00/images/beta-gamma/baltimore-gamma.jpg
2013-01-01 14:35:21.513 00000ee8 Request: cdxnode64.epa.gov:443

It's just a cosmetic issue, but I suspect it's going to confuse people
with some requests logged as "http://site..." and other requests
logged as "site:443"

> It's unexpected (to me) that the incorrect version had any effect
> at all, though, so there probably is another bug somewhere and
> the corrected version might not work either.
>
>> > please temporarily
>> > reduce drain_and_close_socket() to the close_socket() call at the end.
>>
>> That works, but privoxy complains about 'The client side of the
>> connection on socket NNN got closed without sending a complete request
>> line.' when clicking on the link to the 2nd page.
>
> Please send me a a Privoxy log with:
>
> debug 1
> debug 2
> debug 4
> debug 8
> debug 16
> debug 32
> debug 128
> debug 256
> debug 512
> debug 1024
> debug 4096
> debug 8192
> debug 32768
> debug 65536

I saved the log even tho everything seemed to work OK.  Still want it?

> Btw, can you reproduce the problem by clicking around in the
> CGI interface, or only with microsoft.com?

I didn't think to try the CGI interface.  Just tried it with an
unpatched version of privoxy & it happens there also.

microsoft.com was the first example I found that reproduced the
problem every time.  Other places had problems sometimes, but they
didn't happen every time for me.

Thanks,
Lee

------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512