Fossil

Check-in [9c747e1cf3]
Login

Check-in [9c747e1cf3]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:More details on althttpd in the section of www/ssl.wiki that discusses the stunnel + althttpd + fossil serving option used by fossil-scm.org and sqlite.org.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 9c747e1cf33f715764eca740f66c6e5ecd98b706971c0a4ab87ce5723d625af3
User & Date: wyoung 2019-08-07 11:50:12.858
Context
2019-08-07
12:29
Add the LDFLAGS parameter when building the sqlcompttest test program. ... (check-in: 4a15ccdaca user: drh tags: trunk)
11:50
More details on althttpd in the section of www/ssl.wiki that discusses the stunnel + althttpd + fossil serving option used by fossil-scm.org and sqlite.org. ... (check-in: 9c747e1cf3 user: wyoung tags: trunk)
11:34
Add an SQLite compatibility test program and run that program during the "./configure" if the --disable-internal-sqlite option is used in order to verify that the system SQLite library has all of the capabilities that we need. ... (check-in: 350c627a52 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/ssl.wiki.
︙︙
243
244
245
246
247
248
249
250
251

252
253


254

255
256



257
258
259
260
261
262
263


<h3 id="althttpd">stunnel + althttpd</h3>

The public SQLite and Fossil web sites can't just use stunnel + Fossil
because parts of the web site are static, served by
[https://sqlite.org/docsrc/doc/trunk/misc/althttpd.md|a separate web
server called <tt>althttpd</tt>], written by the primary author of both
SQLite and Fossil. It is a lightweight HTTP-only web server. It handles
the static HTTP hits on <tt>sqlite.org</tt> and <tt>fossil-scm.org</tt>,

delegating HTTPS and dynamic Fossil content hits to stunnel and Fossil.



The only documentation for althttpd currently is in its header comment.

As is typical for drh software, althttpd is a single-file C program, so
that at worst, you just have to read its code to understand it.





<h3 id="nginx">nginx</h3>

If your needs are more complex than althttpd can handle or you'd prefer
to use only software available in your server operating system's package
repository, we recommend that you step up to [http://nginx.org/|nginx].








|
|
>
|

>
>
|
>
|
|
>
>
>








243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270


<h3 id="althttpd">stunnel + althttpd</h3>

The public SQLite and Fossil web sites can't just use stunnel + Fossil
because parts of the web site are static, served by
[https://sqlite.org/docsrc/doc/trunk/misc/althttpd.md|a separate web
server called <tt>althttpd</tt>], written by the primary author of both
SQLite and Fossil. <tt>althttpd</tt> is a lightweight HTTP-only web
server. It handles the static HTTP hits on <tt>sqlite.org</tt> and
<tt>fossil-scm.org</tt>, delegating HTTPS hits to stunnel and dynamic
content hits to Fossil.

(The largest single chunk of static content served directly by
<tt>althttpd</tt> rather than via Fossil is the
[https://sqlite.org/docs.html | SQLite documentation], which is built
[https://sqlite.org/docsrc/ | from source files] and then served
statically.)

In addition to the documentation linked above, there is a large header
comment in the [https://sqlite.org/docsrc/file/misc/althttpd.c|single C
file] of <tt>althttpd</tt> which is most helpful.


<h3 id="nginx">nginx</h3>

If your needs are more complex than althttpd can handle or you'd prefer
to use only software available in your server operating system's package
repository, we recommend that you step up to [http://nginx.org/|nginx].
︙︙