From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.ada Subject: Re: Ada in polluted WWW searches Date: Tue, 22 May 2018 15:00:59 -0700 Organization: A noiseless patient Spider Message-ID: <87in7f4ag4.fsf@nightsong.com> References: <871se4rzm3.fsf@jacob-sparre.dk> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: h2725194.stratoserver.net; posting-host="dd5d94a6802641837a7e1095d0ad209e"; logging-data="26972"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/oT9U/ToryAlsOCZbDimNX" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Cancel-Lock: sha1:Ps3mfIDJW53/j1RmjXPW2G71IBQ= sha1:FGVcNNFGbCdq6CiZaoTnoMPrUIA= Xref: reader02.eternal-september.org comp.lang.ada:52603 Date: 2018-05-22T15:00:59-07:00 List-Id: "Randy Brukardt" writes: >> Is the source for the indexing engine available? Maybe somebody could >> be tempted to submit a patch, such that it also can handle HTTPS. > Unfortunately, it's not.... Rather than patching the engine, you could put it behind a reverse proxy that handles https and passes http through. Nginx, apache, pound etc can all do that.