Fossil SCM
Doc touchups.
Commit
aa36afc52c41a6a1c15e7fa8ec9fd97d928bd6140db8adc7931ee696fcdfe5c0
Parent
edfa01d9d20400c…
1 file changed
+10
-8
+10
-8
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -239,22 +239,24 @@ | ||
| 239 | 239 | a sync error. (Prior to 2025-07-21, the protocol permitted multiple |
| 240 | 240 | logins, treating the login as the union of all privileges from all |
| 241 | 241 | login cards. That capability was never used and has been removed.) |
| 242 | 242 | |
| 243 | 243 | As of version 2.27, Fossil supports transfering of the login card |
| 244 | -outside of the payload body, in one of the following ways: | |
| 244 | +externally to the request payload in one of the following ways: | |
| 245 | 245 | |
| 246 | 246 | <ul> |
| 247 | -<li> URL parameter named "x-f-x-l". The value must be URL-encoded. | |
| 248 | -<li> An HTTP header named "X-Fossil-Xfer-Login". The caveat for the | |
| 247 | +<li> URL parameter named "x-f-x-l". | |
| 248 | +<li> An HTTP header named "X-Fossil-Xfer-Login". The caveat for this | |
| 249 | 249 | header is that CGI-hosted fossils cannot see the headers. It |
| 250 | - works for standalone severs and those running via fossil's | |
| 251 | - "test-http" mechanism. This approach is retained, despite the CGI | |
| 252 | - disadvantage, because the URL parameter approach cannot be used | |
| 253 | - to capture sync payload bodies for re-use with the "test-http" | |
| 254 | - mechanism, a capability useful in testing. | |
| 250 | + works for standalone severs and connections running via fossil's | |
| 251 | + "test-http" mechanism. | |
| 255 | 252 | </ul> |
| 253 | + | |
| 254 | +It is legal to use both of those approaches together but it is not | |
| 255 | +possible to use either of them with an in-body login card because | |
| 256 | +including an in-body login card would change the login card's value | |
| 257 | +for the header or URL parameter. | |
| 256 | 258 | |
| 257 | 259 | |
| 258 | 260 | <h3 id="file">3.3 File Cards</h3> |
| 259 | 261 | |
| 260 | 262 | Artifacts are transferred using either "file" cards, or "cfile" |
| 261 | 263 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -239,22 +239,24 @@ | |
| 239 | a sync error. (Prior to 2025-07-21, the protocol permitted multiple |
| 240 | logins, treating the login as the union of all privileges from all |
| 241 | login cards. That capability was never used and has been removed.) |
| 242 | |
| 243 | As of version 2.27, Fossil supports transfering of the login card |
| 244 | outside of the payload body, in one of the following ways: |
| 245 | |
| 246 | <ul> |
| 247 | <li> URL parameter named "x-f-x-l". The value must be URL-encoded. |
| 248 | <li> An HTTP header named "X-Fossil-Xfer-Login". The caveat for the |
| 249 | header is that CGI-hosted fossils cannot see the headers. It |
| 250 | works for standalone severs and those running via fossil's |
| 251 | "test-http" mechanism. This approach is retained, despite the CGI |
| 252 | disadvantage, because the URL parameter approach cannot be used |
| 253 | to capture sync payload bodies for re-use with the "test-http" |
| 254 | mechanism, a capability useful in testing. |
| 255 | </ul> |
| 256 | |
| 257 | |
| 258 | <h3 id="file">3.3 File Cards</h3> |
| 259 | |
| 260 | Artifacts are transferred using either "file" cards, or "cfile" |
| 261 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -239,22 +239,24 @@ | |
| 239 | a sync error. (Prior to 2025-07-21, the protocol permitted multiple |
| 240 | logins, treating the login as the union of all privileges from all |
| 241 | login cards. That capability was never used and has been removed.) |
| 242 | |
| 243 | As of version 2.27, Fossil supports transfering of the login card |
| 244 | externally to the request payload in one of the following ways: |
| 245 | |
| 246 | <ul> |
| 247 | <li> URL parameter named "x-f-x-l". |
| 248 | <li> An HTTP header named "X-Fossil-Xfer-Login". The caveat for this |
| 249 | header is that CGI-hosted fossils cannot see the headers. It |
| 250 | works for standalone severs and connections running via fossil's |
| 251 | "test-http" mechanism. |
| 252 | </ul> |
| 253 | |
| 254 | It is legal to use both of those approaches together but it is not |
| 255 | possible to use either of them with an in-body login card because |
| 256 | including an in-body login card would change the login card's value |
| 257 | for the header or URL parameter. |
| 258 | |
| 259 | |
| 260 | <h3 id="file">3.3 File Cards</h3> |
| 261 | |
| 262 | Artifacts are transferred using either "file" cards, or "cfile" |
| 263 |