Re: problem with SoupContexts

On Wed, 2002-09-04 at 04:52, Joe Shaw wrote:
> On Tue, 2002-09-03 at 19:24, Alex Graveley wrote:
> > I hesitate to take a patch like this, since I think the current behavior
> > is correct... also netscape and mozilla do the same thing.  Can you just
> > access the second uri as a different user?  What harm is there in
> > sending the most recent auth if no username is specified?
> 
> If I understand correctly, the problem is that if you *do* send it as a
> different user, it doesn't use that second user, since the cache isn't
> at all keyed with the user.  At least, that's what Diego's example
> illustrates:
> 
yes this was the problem, it is a quite usual problem when you mispell
the user name or the password. I don't know how it works, but if the
password or user is wrong and an auth error is returned from the server
maybe soup shouldn't cache that uri.

> On Sat, 2002-08-31 at 14:46, Diego González wrote:
> > https://user-p1:p1@localhost:63000/
> > https://user-p2:p1@localhost:63000/
> 
> I think you're right, though, in that it would probably be fine to just
> cache the username.

anyways should i prepare another patch that uses the user and the path
instead of user, password and path?

> 
> Joe
> 
> _______________________________________________
> Soup-list maillist  -  [email protected]
> http://lists.ximian.com/mailman/listinfo/soup-list

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9dovoVdTYZHL1xEIRAr/1AJ90MgjuvmN9voN2eme4Y/8wf707CwCgkCgz
oVno9kyoFZGhZ693n42z9Tw=
=R6xF
-----END PGP SIGNATURE-----