How to Install and Uninstall lighttpd-mod_trigger_b4_dl Package on openSuSE Tumbleweed
Last updated: November 23,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "lighttpd-mod_trigger_b4_dl" package
Please follow the steps below to install lighttpd-mod_trigger_b4_dl on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
lighttpd-mod_trigger_b4_dl
Copied
2. Uninstall "lighttpd-mod_trigger_b4_dl" package
This is a short guide on how to uninstall lighttpd-mod_trigger_b4_dl on openSuSE Tumbleweed:
$
sudo zypper remove
lighttpd-mod_trigger_b4_dl
Copied
3. Information about the lighttpd-mod_trigger_b4_dl package on openSuSE Tumbleweed
Information for package lighttpd-mod_trigger_b4_dl:
---------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : lighttpd-mod_trigger_b4_dl
Version : 1.4.61-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 21,7 KiB
Installed : No
Status : not installed
Source package : lighttpd-1.4.61-1.1.src
Summary : Another anti hot-linking module for Lighttpd
Description :
Anti Hotlinking:
* if user requests download-url directly the request is denied and
he is redirected to ''deny-url'
* if user visits trigger-url before requesting download-url access
is granted
* if user visits download-url again after trigger-timeout has run
down to the request is denied and he is redirected to deny-url
The storage for the trigger information is either stored locally in a
gdbm file or remotly in memcached.
---------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : lighttpd-mod_trigger_b4_dl
Version : 1.4.61-1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 21,7 KiB
Installed : No
Status : not installed
Source package : lighttpd-1.4.61-1.1.src
Summary : Another anti hot-linking module for Lighttpd
Description :
Anti Hotlinking:
* if user requests download-url directly the request is denied and
he is redirected to ''deny-url'
* if user visits trigger-url before requesting download-url access
is granted
* if user visits download-url again after trigger-timeout has run
down to the request is denied and he is redirected to deny-url
The storage for the trigger information is either stored locally in a
gdbm file or remotly in memcached.