Reverse Proxy with local error pages At first create a local directory for serving your customized error pages
# local error pages DocumentRoot /srv/busypage/ Alias /error/ /srv/busypage/ <Directory /srv/busypage/ Options None AllowOverride None Require all granted </Directory> Now put your pages inside and configure your error pages: ProxyErrorOverrideOn ErrorDocument 403 /error/error-403.html ErrorDocument 404 /error/error-404.html ErrorDocument 500 /error/error-500.html ErrorDocument 503 /error/error-503.html So far so easy. Error pages and websockets If you have a websocket in your backend, so this communication should be go through end to end to get the real backend error message.
Read more →
Deliver your websites with Apache and HTTP/2 IMPORTANT INFO !
I’ve backported apache 2.4.25, but it now depends on openssl from debian backports. The reason for this step back is this bug 828236. So you have to add the debian-backports repo in your system:
echo 'deb http://ftp.debian.org/debian jessie-backports main' >> /etc/apt/sources.list.d/debian-backports.list and install/update the openssl packages from there:
apt-get install libssl1.0.0 -t jessie-backports Your system is now ready for the apache 2.
Read more →
Running Apache 2.4 (SID) under Debian wheezy and (squeeze) Apache 2.4 is the current major release. This version is available in the debian SID and Testing tree (experimental before), so I’ve backported these packages to wheezy and in the past squeeze. The last available squeeze-version for i386 in this repro is 2.4.4-6, because I’ve no squezze-i386 servers anymore and I can’t test this packages. The last squeeze-version for amd64 is 2.
Read more →
My servers are mostly work with a normal load, but sometimes they have stress. In some cases the content application like TYPO3 or TomCat could not handle the mass of requests. So I’ve been searched for a automatic solution to display a busy-Page.
The Apache-Modul mod_proxy_balancer provides a solution for me. It doesn’t matter if the content is on the same machine or hosted on dedicated server(s) in the background. The difference is only the source loopback or some foreign IP addresses.
Read more →
Howto grant different rights to users on webdav shares Using webdav is an easy way to share files over
HTTP(S). The Apache Webserver has the modules included. The caveat is the grant concept inside DAV. Under Linux all files are owned by the apache user e. g. www-data, so it is not possible to work with file system rights like MS IIS. If the share ist read only or every autenticated user can write, no problem.
Read more →