Hello, I've just started a branch for exploring a different way to enable the use of HTTP Authorization headers in requests:
http://www.fossil-scm.org/index.html/info/e747041a72 Of course, removing the special character as a flag to enable HTTP Auth could potentially break some users who rely on it at the expense of allowing users who might have # as a legitimate first character in their password. Also, I believe this ticket can be closed: http://www.fossil-scm.org/index.html/tktview?name=c46b0f7bb7 Do we envision more than what Fossil currently does? Perhaps Fossil should just automatically detect a 401 and resend the request? I actually looked at doing that and it was obviously simpler to add a command line option. Now I can clone doing something like: $ fossil clone http://amb@www/~andy/fossil/fossil.cgi/new new.fossil password for amb: remember password (Y/n)? y server says: 401 Authorization Required Clone finished with 246 bytes sent, 622 bytes received server returned an error - clone aborted Oops, looks like I need Authorization: $ fossil clone --httpauth http://amb@www/~andy/fossil/fossil.cgi/new new.fossil password for amb: remember password (Y/n)? y Round-trips: 2 Artifacts sent: 0 received: 15 Clone finished with 642 bytes sent, 2720 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: 018a5f218fdfcaa7400b355e2dc9b8c7c9959588 admin-user: amb (password is "f61fa3") Thoughts? Thanks, Andy -- TAI64 timestamp: 4000000052e8a6dc _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
