Depending on its configuration and installed plugins, the browser may remove or alter (spoof) HTTP referers, thus preventing Shaarli from properly redirecting between pages.
See:
HTTP settings are available by browsing about:config
, here are the available settings and their values.
network.http.sendRefererHeader
- determines when to send the Referer HTTP header
0
: Never send the referring URL
1
: Send only on clicked links2
(default): Send for links and imagesnetwork.http.referer.XOriginPolicy
- Cross-domain origin policy
0
(default): Always send1
: Send if base domains match2
: Send if hosts matchnetwork.http.referer.spoofSource
- Referer spoofing (~faking)
false
(default): real referertrue
: spoof referer (use target URI as referer)
network.http.referer.trimmingPolicy
- trim the URI not to send a full Referer
0
: (default): send full URI1
: scheme+host+port+path2
: scheme+host+portlocalhost
is not a proper Fully Qualified Domain Name (FQDN); if Firefox has
been set up to spoof referers, or only accept requests from the same base domain/host,
Shaarli redirections will not work properly.
To solve this, assign a local domain to your host, e.g.
127.0.0.1 localhost desktop localhost.lan
::1 localhost desktop localhost.lan
and browse Shaarli at http://localhost.lan/.
Related threads:
Delete the file data/config.json.php
and display the page again. You will be asked for a new login/password.
Login form is protected against brute force attacks: 4 failed logins will ban the IP address from login for 30 minutes. Banned IPs can still browse links.
To remove the current IP bans, delete the file data/ipbans.php
The file data/log.txt
shows all logins (successful or failed) and bans/lifted bans.
Search for failed
in this file to look for unauthorized login attempts.
On free.fr: free.fr now supports php 5.6.x(link) and so support now the tag autocompletion but you have to do the following.
At the root of your webspace create a sessions
directory and a .htaccess
file containing:
<IfDefine Free>
php56 1
</IfDefine>
Parse error: syntax error, unexpected '=', expecting '(' in /links/index.php on line xxx
, it means that your host is using php4, not php5. Shaarli requires php 5.1. Try changing the file extension to .php5
If you have the error Warning: file_get_contents() [function.file-get-contents]: URL file-access is disabled in the server configuration in /…/index.php on line xxx
, it means that your host has disabled the ability to fetch a file by HTTP in the php config (Typically in 1and1 hosting). Bad host. Change host. Or comment the following lines:
//list($status,$headers,$data) = getHTTP($url,4); // Short timeout to keep the application responsive.
// FIXME: Decode charset according to charset specified in either 1) HTTP response headers or 2) <head> in html
//if (strpos($status,'200 OK')) $title=html_extract_title($data);
On hosts which forbid outgoing HTTP requests (such as free.fr), some thumbnails will not work.
On lost-oasis, RSS doesn't work correctly, because of this message at the begining of the RSS/ATOM feed : <? // tout ce qui est charge ici (generalement des includes et require) est charge en permanence. ?>
. To fix this, remove this message from php-include/prepend.php
Shaarli tries to sniff the language of the browser (using HTTP_ACCEPT_LANGUAGE
headers)
and choose a date format accordingly. But Shaarli can only use the date formats
(and more generally speaking, the locales) provided by the webserver.
So even if you have a browser in French, you may end up with dates in US format
(it's the case on sebsauvage.net :-( )
This can be caused by several things:
session
directory on the root of your website.) You may need to create the session directory of set it up.sessions
subdirectory and add ini_set('session.save_path', $_SERVER['DOCUMENT_ROOT'].'/../sessions');
. Make sure this directory is not browsable !)Follow the instructions in the error message. Make sure you are accessing shaarli via a direct IP address or a proper hostname. If you have no dots in the hostname (e.g. localhost
or http://my-webserver/shaarli/
), some browsers will not store cookies at all (this respects the HTTP cookie specification).