Please send any requests and complaints to



The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided. Liability claims regarding damage caused by the use of any information provided, including any kind of information which is incomplete or incorrect,will therefore be rejected. All offers are not-binding and without obligation. Parts of the pages or the complete publication including all offers and information might be extended, changed or partly or completely deleted by the author without separate announcement.

The author is not responsible for any contents linked or referred to from his pages - unless he has full knowledge of illegal contents and would be able to prevent the visitors of his site fromviewing those pages. If any damage occurs by the use of information presented there, only the author of the respective pages might be liable, not the one who has linked to these pages. Furthermore the author is not liable for any postings or messages published by users of discussion boards, guestbooks or mailinglists provided on his page.

The author intended not to use any copyrighted material for the publication or, if not possible, to indicate the copyright of the respective object. The copyright for any material created by the author is reserved. Any duplication or use of objects such as images, diagrams, sounds or texts in other electronic or printed publications is not permitted without the author’s agreement.

Privacy policy

If the opportunity for the input of personal or business data (email addresses, name, addresses) is given, the input of these data takes place voluntarily. The use and payment of all offered services are permitted - if and so far technically possible and reasonable - without specification of any personal data or under specification of anonymized data or an alias. The use of published postal addresses, telephone or fax numbers and email addresses for marketing purposes is prohibited, offenders sending unwanted spam messages will be punished.

This disclaimer is to be regarded as part of the internet publication which you were referred from. If sections or individual terms of this statement are not legal or correct, the content or validity of the other parts remain uninfluenced by this fact.

Data Protection

Type of data

The following data will be saved upon requesting a resource from this page: ul li. Your IP-Address at the time of the request. li. Time and type of your request li. Statistics on the reply of the server (Was the resource retrieved correctly? Which size did it have?) li. Information that get’s send by your Browser (Which Browser? Which versions of specific libraries?)

Example of data

This example is entirely made up. A line in my logs might look like this: - - [23/Mar/2019:12:34:56 +0600] "GET /coding HTTP/1.1"
  200 5678 ""
  "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  Chrome/72.0.3626.122 Safari/537.36"

Let’s disassemble this:

  • The IP-address at the time of accessing the page. In theory, it’s possible to find out which landline has been used by connecting this with the date and asking your provider, but in practice this is highly unreliable and unecessary.
  • [23/Mar/2019:12:34:56 +0600] Date, and time of your request. This is stored in the time of the server, so no hints on your timezone can be extracted from this.
  • "GET /coding index HTTP/1.1" This is mainly technical data specifying the request you made. Most interesting is the actual resource you requested, which in this case is the coding-page located at /coding.
  • 200 5678 "" Also technical, this stores information on the servers response. In this case, the request was succesfully served (200), the server returned some data (5678 bytes, to be more exactly), and you reached this page by clicking a link on my index-page.
  • "Mozilla/5.0 (X11; Linux x86_64)… This information is send to me by your Browser. It contains information on which rendering engine you’re using, and which other Browser it is compatible with. Sometimes, the webserver itself uses this to increase the chance of the request being succesfull.

How I use this

Honestly, in most cases I don’t use this. There are, however, some rare cases where I might use this data for one of the following purposes:

  • Blocking malicious Clients like Botnets. For this, usually the IP address and the request time get parsed by an automated tool (running on the same server, so no data will be spoiled here) and if too many requests occured, the IP’s access to the site will get blocked for some time.
  • Load analysis: Time, resource location and server response data can be used to find out about pages that are requested very often.
  • Debugging: If anything went wrong with a specific request, I can use the data to track down if there are problems with compatibility with certain browsers. This requires all of the data * IP and date to track the correct request, everything else to see what could’ve gone wrong and to “replay” the original request.
  • Compatibility analysis: Using automated scripts, I can extract which browsers visit my page most often, mainly to see if certain compatibility hacks are worth the time.