Libelektra: Homepage: Broken URLs
Steps to Reproduce
- Open a web browser
- Open a URL for a plugin like https://www.libelektra.org/plugins/multifile
Expected Result
The web browser displays some information about the multifile plugin.
Actual Result
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /plugins/multifile was not found on this server.</p>
<hr>
<address>Apache/2.4.10 (Debian) Server at www.libelektra.org Port 443</address>
</body></html>
Other Information
The strange thing is that the browser displays the correct result if I follow the steps below.
- Enter the URL https://www.libelektra.org
- Select “Documentation“→“Plugins”
- Select “Multifile“
- The browser shows the correct page content and displays the URL https://www.libelektra.org/plugins/multifile
If I now press enter in the URL input field, then the browser displays the 404 page mentioned above.
sanssecours
All 5 comments
Thank you for reporting this!
Seems like there is still some misconfiguration in the website setup, I am quite sure it worked before reinstallation.
@BernhardDenner Can you take a look at it?
markus2330
on 29 Oct 2017
It seems like an URL rewrite is missing, see https://ngmilk.rocks/2015/03/09/angularjs-html5-mode-or-pretty-urls-on-apache-using-htaccess/
@Namoshek Do you know what exactly we forgot to do in the apache setup?
markus2330
on 29 Oct 2017
I don't remember our exact rewrite rules, but the rules should basically do two things:
- Look if a resource with the given URL is available (e.g. the logo). If this is the case, the resource should be returned (i.e. no rewrite necessary).
- If no resource was found for the given URL, the index.html should be served instead (but the URL should not be changed, i.e. no
Locationheader needs to be sent or so).
The link of you provides proper rewrite conditions, I think. Just give them a try!
Namoshek
on 29 Oct 2017
Found and fixed.
The corresponding Directory directive was pointing to the wrong path, therefore the FallbackResource was not active for the homepage. Now refreshs and direct links work as expected.
BernhardDenner
on 30 Oct 2017
Thank you, that is great!
@BernhardDenner Now only the website build is missing.
markus2330
on 30 Oct 2017
Related issues
markus2330
·
4Comments
mpranj
·
4Comments
dominicjaeger
·
3Comments
e1528532
·
4Comments
sanssecours
·
4Comments
Most helpful comment
Found and fixed.
The corresponding
Directorydirective was pointing to the wrong path, therefore theFallbackResourcewas not active for the homepage. Now refreshs and direct links work as expected.