Bug #159

Lurker list archives show "No matching frontend" errors

Added by chaldene almost 8 years ago. Updated over 4 years ago.

Status:Closed Start:2017-06-19
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:-
Target version:-
Votes: 0

Description

Links from Mailman list infos to the Lurker list archives (e.g. http://lists.bitfolk.com/lurker/list/announce.html) show an error message:

Lurker - failed to render page:

No matching frontend (/usr/share/lurker/www/list/announce.html):

The frontend specified in the webserver configuration does not match any frontend in the lurker config file.

History

#1
Updated by admin almost 8 years ago

  • Status changed from New to In Progress

I see the problem now.

Mailman is using http URLs but my browser (firefox) is respecting the pinned HSTS configuration of bitfolk.com and so redirecting to https before even requesting it. The https version works, but the http version doesn't.

Presumably you are using some browser like Safari which doesn't request https on such domains. I am able to replicate the problem with lynx (!) and will use that to test that I have added server-side redirection to https, for the sake of people with bookmarks and old links.

In the mean time I have corrected the URLs in the Mailman interface to be the https version.

#2
Updated by admin almost 8 years ago

  • Status changed from In Progress to Resolved

The redirect is in place now.

#3
Updated by chaldene almost 8 years ago

Thanks for the fix. I think my browser was missing the HSTS data - I'm using Chrome but with a new browser profile, and had never visited bitfolk.com itself on it. When visiting bitfolk.com, I see the STS header and then lists.bitfolk.com I see the internal browser redirect, so appears to work properly from then on (as does the redirect itself).

#4
Updated by admin over 4 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF