A bit far back, but just for the record:
We need the vendor name of the proxy, when possible.
This is because some proxies might demand a credentials line with every request,
others might not (if I wrote a proxy, I probably would not).
In general, the Proxy-Auth behavior is supposed to be very similar to basic
auth, and what some have told me used to be "credentials manager" in Nav4 would
be responsible for remembering the line, and sending it in the headers of every
request.
In this case, it sounds like your initial request is returned with a 407, so you
get prompted for proxy-auth, which is sent in a re-request.
At this point, I need more information, does the proxy-auth dialog appear with
each HTTP request (for example, a dialog for every inline image in that page),
or does it only happen when you click on links or go to a URL you typed in the
URL field.?
Either way, that might be a problem with the way we manage auth credentials and
network session/connections. If so, this really needs to be a bug if it ever
happens again.
benc
Cihl wrote:
> That's quite strange. I'm behind a authenticating firewall also, and with me
> it only asks once.
>
> Did you check the box right below the user&pass fields (not that it makes
> any difference with me, but maybe it works for you)?
>
> By the way, do you get any proxy errors when surfing? I have this problem
> that i regularly have to hit the reload-button once or twice to get the page
> instead of a proxy error.
>
> <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > I'm seeing this on the Dec. 24 build on Linux and Windows NT; also on the
> > previous two milestones.
> >
> > We have an authenticating proxy server at 10.8.254.55; all other browsers
> > ask *once* for the userid/password for the proxy server at 10.8.254.55 and
> > then connect to whatever URLs are fed in.
> >
> > Mozilla asks for the userid/password for "proxy server at <insert url
> > here>" for each and every url accessed. This is major broke, and makes
> > mozilla unusable here.
> >
> > All I know about the proxy server is that it's on a BSDI firewall
> > administered by esoft.
> >
> > I've tried to beat my way through bugzilla to see if there's an open bug
> > report for this, with no luck -- but I do see that most proxy-related bugs
> > are at P3. I have to state that this is a *showstopper* here.
> >
> > Is there a workaround I'm missing?
> >
> > T Kauffman
> >
