Fossil SCM
Replace a couple old references to fossil-scm.org/fossil with /home.
Commit
ca5ecf2223e7b2e95ab68c3d7698934691e24e4b48382c17fb6738efe0804868
Parent
c953e01c9e0155b…
1 file changed
+3
-3
+3
-3
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -150,24 +150,24 @@ | ||
| 150 | 150 | |
| 151 | 151 | The client modifies the URL by appending the method name "<b>/xfer</b>" |
| 152 | 152 | to the end. For example, if the URL specified on the client command |
| 153 | 153 | line is |
| 154 | 154 | |
| 155 | -<pre>https://fossil-scm.org/fossil</pre> | |
| 155 | +<pre>https://fossil-scm.org/home</pre> | |
| 156 | 156 | |
| 157 | 157 | Then the URL that is really used to do the synchronization will |
| 158 | 158 | be: |
| 159 | 159 | |
| 160 | -<pre>https://fossil-scm.org/fossil/xfer</pre> | |
| 160 | +<pre>https://fossil-scm.org/home/xfer</pre> | |
| 161 | 161 | |
| 162 | 162 | <h3 id="req-format">2.2 HTTP Request Format</h3> |
| 163 | 163 | |
| 164 | 164 | The client always sends a POST request to the server. The |
| 165 | 165 | general format of the POST request is as follows: |
| 166 | 166 | |
| 167 | 167 | <pre> |
| 168 | -POST /fossil/xfer HTTP/1.0 | |
| 168 | +POST /home/xfer HTTP/1.0 | |
| 169 | 169 | Host: fossil-scm.hwaci.com:80 |
| 170 | 170 | Content-Type: application/x-fossil |
| 171 | 171 | Content-Length: 4216 |
| 172 | 172 | </pre> |
| 173 | 173 | |
| 174 | 174 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -150,24 +150,24 @@ | |
| 150 | |
| 151 | The client modifies the URL by appending the method name "<b>/xfer</b>" |
| 152 | to the end. For example, if the URL specified on the client command |
| 153 | line is |
| 154 | |
| 155 | <pre>https://fossil-scm.org/fossil</pre> |
| 156 | |
| 157 | Then the URL that is really used to do the synchronization will |
| 158 | be: |
| 159 | |
| 160 | <pre>https://fossil-scm.org/fossil/xfer</pre> |
| 161 | |
| 162 | <h3 id="req-format">2.2 HTTP Request Format</h3> |
| 163 | |
| 164 | The client always sends a POST request to the server. The |
| 165 | general format of the POST request is as follows: |
| 166 | |
| 167 | <pre> |
| 168 | POST /fossil/xfer HTTP/1.0 |
| 169 | Host: fossil-scm.hwaci.com:80 |
| 170 | Content-Type: application/x-fossil |
| 171 | Content-Length: 4216 |
| 172 | </pre> |
| 173 | |
| 174 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -150,24 +150,24 @@ | |
| 150 | |
| 151 | The client modifies the URL by appending the method name "<b>/xfer</b>" |
| 152 | to the end. For example, if the URL specified on the client command |
| 153 | line is |
| 154 | |
| 155 | <pre>https://fossil-scm.org/home</pre> |
| 156 | |
| 157 | Then the URL that is really used to do the synchronization will |
| 158 | be: |
| 159 | |
| 160 | <pre>https://fossil-scm.org/home/xfer</pre> |
| 161 | |
| 162 | <h3 id="req-format">2.2 HTTP Request Format</h3> |
| 163 | |
| 164 | The client always sends a POST request to the server. The |
| 165 | general format of the POST request is as follows: |
| 166 | |
| 167 | <pre> |
| 168 | POST /home/xfer HTTP/1.0 |
| 169 | Host: fossil-scm.hwaci.com:80 |
| 170 | Content-Type: application/x-fossil |
| 171 | Content-Length: 4216 |
| 172 | </pre> |
| 173 | |
| 174 |