Jan Danielsson wrote:
Hello,
This has been brought up before, and I've been meaning to look at it,
but it suddenly became a little more urgent. Last week I found myself
being in a situation of not being able to clone a https repository due
to an evil http proxy, and soon afterwards someone I know ran into the
same problem at his workplace.
I was planning on adding support for https over http-proxy this past
weekend, but other things got in the way. I did however take a quick
look and noticed that the code currently makes certain assumptions which
makes it a little less trivial than it could have been -- so slight
rewiring is required.
The usual check, to avoid duplicate work: Is anyone else working on
this already?
Is anyone planning on touching the ssl and/or http-proxy code in the
very near future?
I recall seeing this bug/patch a while back:
http://fossil-scm.org/index.html/tktview?name=e854101c4f
But it's really old, so it's probably not going to apply to the current
version cleanly.
-J
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
