| Comment: | Release 0.3.21
A multi-check-in fossil push lands; --httptrace reaches a zit server. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | version-0.3.21 |
| Files: | files | file ages | folders |
| SHA3-256: |
575cd3fcdd80c8d09b7ab3a22431d953 |
| User & Date: | dmestas on 2026-09-17 19:12:48.035 |
| Other Links: | manifest | tags |
|
2026-09-18
| ||
| 01:45 |
sync: clone and pull send a login card
Only push and sync signed a login, so a private repository on a forge that gates reads was unreadable by the account that owned it, and a stored login sat unused while pull read anonymously. All four verbs now resolve the login the same way: --user, the URL's user@, then the stored login. A clone holds name and password until the round-0 reply teaches the project code, then signs every later round; a refused round 0 that taught the code is retried with the login, as fossil's client does. The accepted login is stored in the clone. A URL user with no password source is a hint and goes anonymous with a note; --user without a password is an error. Smoke S17 drives a read-gated fossil. check-in: 1d5a6c8fa7 user: dmestas tags: trunk | |
|
2026-09-17
| ||
| 19:12 |
Release 0.3.21
A multi-check-in fossil push lands; --httptrace reaches a zit server. check-in: 575cd3fcdd user: dmestas tags: trunk, version-0.3.21 | |
| 19:06 |
serve: accept application/x-fossil-debug
fossil --httptrace sends its cards uncompressed under this type, and the server refused it with a bare 415 on the premise that the reference client never sends it. The exchange now tells handleXfer whether the body is a zlib container or plain cards; the reply is framed as before, and fossil reads the reply's framing off the reply's own content type. x-fossil-uncompressed stays reply-only. check-in: cc96464a51 user: dmestas tags: trunk | |