54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
side, each request is independent. The server does not preserve
any information about the client from one request to the next.</p>
<h4>2.0.1 Encrypted Transport</h4>
<p>In the current implementation of Fossil, the server only
understands HTTP requests. The client can send either
clear-text HTTP requests or or encrypted HTTPS requests. But when
HTTPS requests are sent, they first must be decrypted by a webserver
or proxy before being passed to the Fossil server. This limitation
may be relaxed in a future release.</p>
<h3>2.1 Server Identification</h3>
<p>The server is identified by a URL argument that accompanies the
|
|
|
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
side, each request is independent. The server does not preserve
any information about the client from one request to the next.</p>
<h4>2.0.1 Encrypted Transport</h4>
<p>In the current implementation of Fossil, the server only
understands HTTP requests. The client can send either
clear-text HTTP requests or encrypted HTTPS requests. But when
HTTPS requests are sent, they first must be decrypted by a webserver
or proxy before being passed to the Fossil server. This limitation
may be relaxed in a future release.</p>
<h3>2.1 Server Identification</h3>
<p>The server is identified by a URL argument that accompanies the
|