[
https://issues.apache.org/jira/browse/LUCENE-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045577#comment-17045577
]
Michael McCandless commented on LUCENE-9227:
--------------------------------------------
{quote}Is [~mikemccand]'s Lucene Search engine based on pure Lucene still
available and maintained (with HTTPS)?
{quote}
The only Lucene based search engine I'm currently personally running in
production is
[jirasearch.mikemccandless.com|http://jirasearch.mikemccandless.com/search.py?index=jira],
for searching all Lucene/Solr/Tika/Infra Jira issues ... it tries to
showcase/dog food a number of fun pure Lucene features ... [blog post
here|http://blog.mikemccandless.com/2016/10/jiraseseach-20-dog-food-using-lucene-to.html].
But, alas, it's still HTTP only :(
> Make page ready for pure HTTPS
> ------------------------------
>
> Key: LUCENE-9227
> URL: https://issues.apache.org/jira/browse/LUCENE-9227
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Blocker
>
> The web page can currently be visited using HTTPS but this brings warning:
> - Both search providers create a form that passes USER ENTERED INPUT using no
> encryption. This is not allowed due to GDPR. We have to fix this asap. It
> looks like [~otis] search is working with HTTPS (if we change domain name),
> but the Lucidworks does not
> - There were some CSS files loaded with HTTP (fonts from Google - this was
> fixed)
> Once those 2 problems are fixed (I grepped for HTTP and still found many
> links with HTTP, but looks like no images or scripts or css anymore), I'd
> like to add a permanent redirect http://lucene.apache.org/ ->
> https://lucene.apache.org to the htaccess template file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
