<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Webserver on ads' corner</title><link>https://andreas.scherbaum.la/tags/webserver/</link><description>Recent content in Webserver on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Dec 2022 17:21:00 +0100</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/webserver/index.xml" rel="self" type="application/rss+xml"/><item><title>Using fail2ban to block unfriendly web requests</title><link>https://andreas.scherbaum.la/post/2022-12-09_using-fail2ban-to-block-unfriendly-web-requests/</link><pubDate>Fri, 09 Dec 2022 17:21:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2022-12-09_using-fail2ban-to-block-unfriendly-web-requests/</guid><description>&lt;p&gt;Every time I peek into the webserver logfiles, I find quite a few 404 requests trying to figure out if certain exploits exist on this server. Now I get that these are automated attempts, and the number of requests coming from one IP show that they try several different exploits and path names. Nevertheless I thought that I don’t need this in my log, and on my webserver. &lt;a href="https://www.fail2ban.org/"&gt;fail2ban&lt;/a&gt; for the rescue.&lt;/p&gt;</description></item><item><title>Monitor website status with Huginn</title><link>https://andreas.scherbaum.la/post/2020-10-14_monitor-website-status-with-huginn/</link><pubDate>Wed, 14 Oct 2020 22:04:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-10-14_monitor-website-status-with-huginn/</guid><description>&lt;p&gt;After setting up &lt;em&gt;&lt;a href="https://github.com/huginn/huginn"&gt;Huginn&lt;/a&gt;&lt;/em&gt;, and implementing the actions on my todo list, I had a look at the available agents and started thinking what else they can be useful for.&lt;/p&gt;&#10;&lt;p&gt;One of the ideas I came up with is monitoring if a website is available, or has some trouble. I already have a monitoring system in place, but it&amp;rsquo;s a nice exercise to learn more about the other agents.&lt;/p&gt;</description></item><item><title>openHAB: redirect port 8080 to port 80</title><link>https://andreas.scherbaum.la/post/2018-07-15_openhab-redirect-port-8080-to-port-80/</link><pubDate>Sun, 15 Jul 2018 22:59:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2018-07-15_openhab-redirect-port-8080-to-port-80/</guid><description>&lt;p&gt;The &lt;a href="https://www.openhab.org/"&gt;openHAB&lt;/a&gt; &lt;a href="https://www.raspberrypi.org/"&gt;Raspberry&lt;/a&gt; &lt;a href="https://docs.openhab.org/installation/openhabian.html"&gt;image&lt;/a&gt;, by default, listens on port 8080. After &lt;a href="https://andreas.scherbaum.la/categories/openhab"&gt;using the image for a while&lt;/a&gt;, it became quite boring to always add the port to the URL. Quickly I decided to redirect port &lt;code&gt;80&lt;/code&gt; to port &lt;code&gt;8080&lt;/code&gt;, and make my life easier.&lt;/p&gt;&#10;&lt;p&gt;Not sure how much work that is in the &lt;em&gt;openHAB&lt;/em&gt; settings, I settled with redirecting or forwarding the port &lt;code&gt;80&lt;/code&gt; to port &lt;code&gt;8080&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Stupid open_basedir handling in PHP</title><link>https://andreas.scherbaum.la/post/2008-04-29_stupid-open_basedir-handling-in-php/</link><pubDate>Tue, 29 Apr 2008 00:15:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2008-04-29_stupid-open_basedir-handling-in-php/</guid><description>&lt;p&gt;I have an application which has to run on different webservers (or to be more specific on servers with a different directory layout). On one servers the &lt;code&gt;php&lt;/code&gt; files are in &lt;code&gt;/usr/home&lt;/code&gt;, the next one is using &lt;code&gt;/www&lt;/code&gt;, the third one &lt;code&gt;/var/www&lt;/code&gt; and last but not least my laptop has the files in my home directory which is under &lt;code&gt;/home&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;No problem - or?&lt;/p&gt;</description></item></channel></rss>