Re: [proxyTools-users] escaping a very restrictive

[Michael F. <Mic...@tb...>]

> [...]
> > Got this result - this make more sense ?? Still looks odd to me.....
> >
> > C:\Program Files\localproxy>perl statproxy.pl -t all -a ,192.168.4.1,michael,******
> > 192.168.4.1:8080
> >
> > statProxy v4.105 report from 192.168.4.67:
> > 192.168.4.1     :8080  AFFFFFFFFFFFF FFFFF  0.0/?
>
> This is the right proxy, at least. You got a response this time.
> The first test shows 'A'uthentication was required (and it failed).
> The rest failed for the same reason.
> I hope you tell me that you just entered the wrong password. :-)
> Did you have the credentials correct in the environment too
> (shouldn't be needed, but if there's a conflict you might have
> triggered a new bug)?
>
> Again, I don't think I have changed anything that should affect the
> authentication. Do you still have the old statProxy? Does that one
> work?
>
> > Mike
>

Nope double checked the password.

First the current version of statprox - still fails.

C:\Program Files\localproxy>perl statproxy.pl -t all -a ,192.168.4.1,michael,******
192.168.4.1:8080

statProxy v4.105 report from 192.168.4.67:
192.168.4.1     :8080  AFFFFFFFFFFFF FFFFF  0.1/?

Then an old version.

C:\Program Files\localproxy>oldstatprox

C:\Program Files\localproxy>perl oldstatproxy.pl -t all -a ,192.168.4.1,michael,
****** 192.168.4.1:8080
"nonBlockingConnect" is not exported by the WLib module at oldstatproxy.pl line
28
Can't continue after import errors at oldstatproxy.pl line 28
BEGIN failed--compilation aborted at oldstatproxy.pl line 30.

C:\Program Files\localproxy>


Must be a *dud* old version of statproxy so I reused one from the 2002-06-14 distribution of
proxytools.

Same error, maybe that was that version I was using.
Try 2002-08-02.

Nope... still the same result - Wlib.pm has changed I guess - one last try
2002-09-04 which was the previous version I guess (wasn`t that bugged ??)

C:\Program Files\localproxy>perl oldstatproxy.pl -t all -a ,192.168.4.1,michael,
****** 192.168.4.1:8080

statProxy v4.95 report from 192.168.4.67:
192.168.4.1     :8080  AFFFFFFFFFFFF FFFFsend() on closed socket PROXY at oldsta
tproxy.pl line 1016.
Your vendor has not defined POSIX macro EWOULDBLOCK, used at oldstatproxy.pl lin
e 1017

C:\Program Files\localproxy>

Yup - thats the old error isn`t it ??

So not much luck on testing with an old version of statproxy. Now I could use an old entire
distribution... bugger, I`ll try that.

C:\Program Files\localproxy>cd ..

C:\Program Files>cd lp.bak

C:\Program Files\lp.bak>statprox

C:\Program Files\lp.bak>perl statproxy.pl -t all -a ,192.168.4.1,michael,******
 192.168.4.1:8080

statProxy v4.91 report from 192.168.4.67:
192.168.4.1     :8080  AFFFFFFFFFFFF FFFFF  1.9/?
Reference page size was 534 bytes


C:\Program Files\lp.bak>

OK - same result (but done a lot slower) using the August distribution (08 !!).

So it looks like something has changed on my system as this used to work - damn.

Hmmm - better check my environment variables and check they are set up right and ping dav-serv
to make sure it hasn`t changed - our `system` is in a constant state of flux so nothing can be
relied on.

Ping dav-serv = 192.168.4.1

Environment variables :

SET HTTP_proxy=http://192.168.4.1:8080
SET HTTP_proxy_user=michael
SET HTTP_proxy_pass=******
SET HTTP_proxy_realm=dav-serv.tbsmerchants.co.uk

looks alright to me....

Note that the `rules` for the Superscout proxy server have changed and it is now much stricter
as to what it is supposed to allow (although as noted some ports now appear to be open!!).

In theory that *shouldn`t* affect basic authentication though - unless statproxy.pl is trying
to conenct to a specific site (previously unblocked) and the `blocked` error it now thinks of
as an authentication failure ??

Hmmm... looking through and seeing if theres anything else I can do to provide useful
information - guess I`ll run localproxy with debug=3 and see what it says when trying to
connect - see if it reports authentication errors or just the usual problems of trying to find
a proxy it can reach. As far as I can remember if I point IE to localhost:10080 with lp
running the error is Superscout Blocked *NOT* authentication failed which would indicate to me
that lp is passing on the authentications trings from the environment/config fine... but its
worth double checking.

Mike