Ja, https://markohoven.com/ is verhuisd naar https://markohoven.com/
Hoe doe je dit nu op een correcte manier?
Binnen IIS kan dit met web.config

<?xml version="1.0" encoding="UTF-8"?>
  <httpRedirect enabled="true" destination="https://markohoven.com" httpResponseStatus="Permanent" />
  <defaultDocument enabled="true">
    <clear />
     <add value="index.php" />
     <add value="index.htm" />
     <add value="index.html" />
     <add value="default.asp" />
     <add value="default.aspx" />
     <add value="default.htm" />
     <add value="default.html" />
   <httpErrors errorMode="Custom">
    <remove statusCode="404" subStatusCode="-1" />
    <error statusCode="404" prefixLanguageFilePath="" path="/index.php" responseMode="ExecuteURL" />

Een andere mogelijkheid is in code… Continue reading 301-redirect


The Internet is an increasingly complex place, not just in terms of services but also from a technical standpoint, especially with the advent of mobile devices over the past few years.

Everything that happens on the web, from browsing, streaming and messaging to file sharing, downloads and, more recently, backups, is based on protocols that have long started to show their age.

Efforts from Internet giants like Google and Microsoft are aimed at improving the situation, but given the slow rate of standardization and adoption of new protocols (or even extensions to existing protocols), it looks like the process will take a long time.

Email is one of the oldest Internet-based conveniences, just like most of the protocols used to make it all happen: SMTP, POP3 and IMAP. Today we’ll deal with IMAP, which is currently at version 4 revision 1, as standardized by the 12-year-old RFC 3501. Continue reading Thunderbird

419 HTTP status code

… does not exist

However it did take some of my time to figure this one out as the response code was really in my webserver logfiles and as usual… I was not the first to run into this problem, see: https://stackoverflow.com/questions/46266553/why-laravel-api-return-419-status-code-on-post-and-put-method

You get a 419 status code, if an (external) script tries to post to your Laravel application, without the o-so-needed CSRF token.

First option is to change in App\Http\Middleware\VerifyCsrfToken:
protected $except = [ ‘/*’, ];
(or maybe something more specific and a little more safe, like ‘/myapiurl/*’,)

Second option is to put the route in api.php instead of web.php, but that implies prefixing all your routes with /api/

… your choice!

The Joel Test

bron: click here.

The Joel Test: 12 Steps to Better Code

Have you ever heard of SEMA? It’s a fairly esoteric system for measuring how good a software team is. No, wait! Don’t follow that link! It will take you about six years just to understand that stuff. So I’ve come up with my own, highly irresponsible, sloppy test to rate the quality of a software team. The great part about it is that it takes about 3 minutes. With all the time you save, you can go to medical school.

The Joel Test

  1. Do you use source control?
  2. Can you make a build in one step?
  3. Do you make daily builds?
  4. Do you have a bug database?
  5. Do you fix bugs before writing new code?
  6. Do you have an up-to-date schedule?
  7. Do you have a spec?
  8. Do programmers have quiet working conditions?
  9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

Continue reading The Joel Test