2013/10/28 Jan Nijtmans <jan.nijtm...@gmail.com>:
> >fossil sync https://jan.nijtmans:*********@www.fossil-scm.org/fossil
> via proxy: http://130.139.104.40:8080
.....
> So, if this little thing could be fixed as well, it would be perfect!
Follow-up: If I do the same without specifying the password in the url:
>fossil sync https://jan.nijtm...@www.fossil.org/fossil
password for jan.nijtmans: *********
remember password (Y/n)? Y
via proxy: http://130.139.104.40:8080
Round-trips: 1 Artifacts sent: 0 received: 0
Sync finished with 1256 bytes sent, 1073 bytes received
>fossil sync
Sync with https://jan.nijtm...@www.fossil-scm.org/fossil
via proxy: http://130.139.104.40:8080
Round-trips: 1 Artifacts sent: 0 received: 74
Sync finished with 1270 bytes sent, 3107 bytes received
So, then it works! Trying the same with stock fossil:
>fossil sync https://jan.nijtm...@www.fossil.org/fossil
password for jan.nijtmans: *********
remember password (Y/n)? Y
via proxy: http://130.139.104.40:8080
Round-trips: 1 Artifacts sent: 0 received: 0
server says: 503 Service Unavailable
Sync finished with 1286 bytes sent, 970 bytes received
that doesn' t work, but we already knew that.
Conclusion: your branch works fine as long as the password is
not taken from the (https) url.
I hope this feedback is useful to you.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
